From owner-freebsd-current@freebsd.org Mon Jan 29 23:02:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05775EE3B7D for ; Mon, 29 Jan 2018 23:02:15 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BF786B6E9 for ; Mon, 29 Jan 2018 23:02:14 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 861BA120DA; Tue, 30 Jan 2018 00:02:07 +0100 (CET) From: Dimitry Andric Message-Id: <0B0D5F42-8A40-4E00-812C-EFB6556E9444@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_F9AD0379-E10A-4F99-8D01-5D168C29FC5C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11 Date: Tue, 30 Jan 2018 00:01:57 +0100 In-Reply-To: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de> Cc: FreeBSD CURRENT To: "O. Hartmann" References: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 23:02:15 -0000 --Apple-Mail=_F9AD0379-E10A-4F99-8D01-5D168C29FC5C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 29 Jan 2018, at 19:39, O. Hartmann wrote: >=20 > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 = and performed > updates of the ports tree. Since Sunday, I receive segmenatation = faults (SIG 11) when > accessing the server, especially with setup of nextcloud, refdb, = phpldapadmin and any > other access with LDAP backend (all https). >=20 > The message on console is: >=20 > pid 23108 (httpd), uid 80: exited on signal 11 > pid 32283 (httpd), uid 80: exited on signal 11 > pid 21286 (httpd), uid 80: exited on signal 11 > pid 10292 (httpd), uid 80: exited on signal 11 >=20 > I do not see anything else! Neither in the log (no matter what log = level I switch on) nor > elsewhere. >=20 > Configuration hasn't changed. >=20 > What the ... is up with the system? How can I dig into the problem? Try debugging httpd, e.g.: sudo /usr/local/sbin/httpd -X then "run", and see if you can get a backtrace. -Dimitry --Apple-Mail=_F9AD0379-E10A-4F99-8D01-5D168C29FC5C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWm+n7gAKCRCwXqMKLiCW o60yAJ97H664CSKWoDDPzBfW/KND1fqZ4wCfeg97B9MOSCLq/a2b6fzJzvne6tQ= =vntf -----END PGP SIGNATURE----- --Apple-Mail=_F9AD0379-E10A-4F99-8D01-5D168C29FC5C--