CURRENT, CLANG 6: apache24, uid 80: exited on signal 11
Dimitry Andric
dim at FreeBSD.org
Mon Jan 29 23:09:10 UTC 2018
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 223 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freebsd.org/pipermail/freebsd-current/attachments/20180130/024223d5/attachment.sig>
More information about the freebsd-current
mailing list