Apache log entry- what is this?
 

I once again found something odd in my apache log files. I am just wondering if this is something to be concerned about. It looks as though apache was restarted but I have not restarted it for a week or so. Im wondering what would have made it restart. Here are the entries

error log:
[Sun Jan 12 04:02:13 2003] [notice] Apache/1.3.23 (Unix) (Red-Hat/Linux) configured -- resuming normal operations
[Sun Jan 12 04:02:13 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Jan 12 04:02:13 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)

access log:
[Sun Jan 12 04:02:10 2003] [warn] child process 1127 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1128 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1129 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1130 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1131 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1132 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1133 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1134 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1267 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1557 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1986 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1987 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1988 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 1989 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 4514 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 4515 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:10 2003] [warn] child process 4516 did not exit, sending another SIGHUP
[Sun Jan 12 04:02:12 2003] [notice] SIGHUP received. Attempting to restart
[Sun Jan 12 04:02:13 2003] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName

same problem here
 

I have the exact same problem....

.... he starts doing this for a while, then all of a sudden httpd dies.... and has to be restarted manually...

I really need to solve this problem, but have no idea how to do so... the error message tells me nothing!! :confused:

My log looks like this:

[Wed Sep 10 04:02:09 2003] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux) PHP/4.0.4pl1 mod_throttle/3.1.2 configured -- resuming normal operations
[Wed Sep 10 04:02:09 2003] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Sep 10 04:02:09 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Thu Sep 11 04:02:09 2003] [warn] child process 3034 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3035 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3038 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3039 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3040 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3041 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3042 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 3043 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 5507 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 5590 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [warn] child process 5774 did not exit, sending another SIGHUP
[Thu Sep 11 04:02:09 2003] [notice] SIGHUP received. Attempting to restart

This goes on until httpd dies....

Should I update mod_throttle?? SIGHUP, as far as I know, is just a kill -1, which of course cannot work if the process as such is not in existence. The questio is, why does he think it should exist in the first place? And why does Apache not simply say: ok, cannot kill, because does not exist, so ignore?