Hi List,
after latest update of httpd, mod_ssl, httpd-suexec our
WMS stopped working, glite-wms-wmproxy dying 16 hours
later according to nagios test WMProxy-CertLifetime.
Attemp to restart services and even to reboot the machnie
doesn't help.
trying to start by hand via:
/opt/glite/etc/init.d/glite-wms-wmproxy start
got me funny:
/usr/sbin/httpd -k start -f /opt/glite/etc/glite_wms_wmproxy_httpd.conf
/opt/glite/etc/init.d/glite-wms-wmproxy: line 42: 19331 Segmentation fault
$httpdpath -k $@ -f $config
To get further investigation I've run /usr/sbin/httpd via gdb:
gdb /usr/sbin/httpd
.
.
.
(gdb) start -k start -f /opt/glite/etc/glite_wms_wmproxy_httpd.conf
.
.
.
[Switching to Thread -1208866592 (LWP 19933)]
0x00239c0d in main () from /usr/sbin/httpd
(gdb) c
Continuing.
(no debugging symbols found)
.
.
.
Program received signal SIGSEGV, Segmentation fault.
0x00d214e5 in sitecast_responder () from /usr/lib/httpd/modules/mod_gridsite.so
We run with the latest:
httpd-2.0.52-41.sl4.7
mod_ssl-2.0.52-41.sl4.7
from SL48 errata repository.
Does it mean gridsite-apache uncompatible with the latest
httpd/mod_ssl on SL4 now?
Taking into account what is in:
http://kbase.redhat.com/faq/docs/DOC-20491
it could be the reason.
--
Best regards,
Valery Mitsyn
|