Date: Tue, 30 Jan 2018 00:01:57 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11 Message-ID: <0B0D5F42-8A40-4E00-812C-EFB6556E9444@FreeBSD.org> In-Reply-To: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de> References: <20180129194025.745c49bd@thor.intern.walstatt.dynvpn.de>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On 29 Jan 2018, at 19:39, O. Hartmann <ohartmann@walstatt.org> wrote: > > 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). > > The message on console is: > > 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 > > I do not see anything else! Neither in the log (no matter what log level I switch on) nor > elsewhere. > > Configuration hasn't changed. > > 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 [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWm+n7gAKCRCwXqMKLiCW o60yAJ97H664CSKWoDDPzBfW/KND1fqZ4wCfeg97B9MOSCLq/a2b6fzJzvne6tQ= =vntf -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0B0D5F42-8A40-4E00-812C-EFB6556E9444>