Why a SIGHUP signal to httpd kills the tomcat process?

Posted by Geo on Server Fault See other posts from Server Fault or by Geo
Published on 2009-07-24T14:56:13Z Indexed on 2010/05/26 23:41 UTC
Read the original article Hit count: 414

Filed under:
|
|
|
|

I have a server with a tomcat process binding to port 80 and a httpd processes binding to port 5000. For some reason every time any process send a SIGHUP signal to httpd process my tomcat process disappears without error or anything.

I fixed the issue on the server the following way, added an explicit ServerName directive in the httpd.conf and that fixed the issue.

I still don't understand why the SIGHUP to httpd killed the tomcat process.

NOTE 1: I replicated the kill signal with the following command:

find out what the httpd pid is.

cat /etc/httpd/run/httpd.pid
4056

then kill with a sighup signal

kill -s SIGHUP 4056

NOTE 2: We troubleshoot the issue and find that logrotate running every morning at 4am was sending a SIGHUP signal to realease the logs to be able to rotate them, thus killing tomcat as well.

© Server Fault or respective owner

Related posts about linux

Related posts about apache