Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

From: Dimitry Andric <dim_at_FreeBSD.org>
Date: Tue, 30 Jan 2018 00:09:07 +0100
On 30 Jan 2018, at 00:01, Dimitry Andric <dim_at_FreeBSD.org> wrote:
> 
> On 29 Jan 2018, at 19:39, O. Hartmann <ohartmann_at_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

I meant "sudo gdb /usr/local/sbin/httpd -X", sorry.

-Dimitry


Received on Mon Jan 29 2018 - 22:09:10 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC