<snip> > > Problem: > > Apache dies unexpected and out of the blue. e.g. I came to work this > > (monday) morning, > > and found my webserver died about half an hour before I even got into > > the office. > > Every so often (seemingly random times...) therewill be entries in the > > error_log saying: > > [notice] caught SIGTERM, shutting down > > [notice] Apache/2.0.54 (Unix) PHP/4.3.11 configured -- resuming normal > > operations > > SIGTERM is the standard unix signal to kill a process. This is exactly the > log message you get if you type "apachectl stop" or "kill <PID>". So > something must be doing this... > > You say the times are random - are you certain? Check in the crontab for root > to see if there is a forgotten instruction to stop apache (check all the > other crontabs if apache doesn't start as root). >
--------------- Yes times seem to be random, sometimes the server will die within several minutes from being started, sometimes will be anything between 10 minutes and 40, 50 minutes. ----------- > I notice below that the SIGTERM is followed immediately by a start and then > by another SIGTERM - could there be a rogue daemon running - maybe to rotate > logs or something? Check it out. > ------------- I have no reasonable explanation for this as of yet. When I got to work on monday morning, I looked through the log file, and there were a *lot* of [notice] caught SIGTERM, shutting down [notice] Apache/2.0.54 (Unix) PHP/4.3.11 configured -- resuming normal lines in there. This is extremely odd, as the webserver ofcourse doesn't get used on the weekend as it is my workstation (I'm a web developer). the only thing I could think of was a misbehaving profiler or module. The only things I added before the server started dying was a virtualhost and mod_auth. I have tested with disabling the vhost, mod_auth and Xdebug (PHP profiler/debugger). None of these seem to give me a solution. So I am still stuck with a sporadically dying webserver. When I get back to work in the morning I will however make sure that there are no crontabs set. I am 99.9 % sure there aren;t as I am the only one that uses my machine. Would their be any other way to find out what exactly happens that would kill the server ? ------------- > Rgds, > Owen Boyle > Disclaimer: Any disclaimer attached to this message may be ignored. > <snip> -- "If you really want something in this life, you have to work for it. Now, quiet! They're about to announce the lottery numbers..." - Homer Simpson --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
