You are not logged in.
I have apache, acting as a proxy (ssl+gssapi) for sogo (www.sogo.nu)
everything went fine, until all of a sudden (no configuration change) sogo stopped working (user gets ERR_EMPTY_RESPONSE in browser).
in error_log, since May 21, I get the following entry every time someone tries to access Sogo:
[Sun May 28 19:07:28.287343 2017] [core:notice] [pid 504:tid 140255993166784] AH00052: child pid 19543 exit signal Segmentation fault (11)
sogo itself, nor its config has changed
same applies to the config of apache. The server is -apart from package updates- very stable.
when attaching gdb to the apache httpd process I get the following info:
Thread 2 "httpd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fea408be700 (LWP 22639)]
0x00007fea42de35d5 in EVP_MD_CTX_clear_flags () from target:/usr/lib/libcrypto.so.1.1
the change from openssl 1.0 to 1.1 was the only significant change on this server in May, so it could be this is what is causing the segmentation fault. but I wonder what to do next?
edit: narrowed issue down to mod_auth_gssapi
Last edited by kvtb (2017-06-01 18:51:49)
Offline
I was stupid, I forgot I had a custom module (self compiled) mod_auth_gssapi - which needed to be recompiled
Offline