Why a SIGHUP signal to httpd kills the tomcat process?
- by Geo
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.
