PDA

View Full Version : Shut down Errors in logs



firebirdfan
12-07-2003, 11:34 PM
I get this in my Error logs daily - what's it all about ?

[Fri Dec 5 19:55:32 2003] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux) PHP/4.3.0 configured -- resuming normal operations
[Fri Dec 5 19:55:32 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Fri Dec 5 19:55:35 2003] [warn] (95)Operation not supported: setsockopt: (TCP_NODELAY)

andy
12-18-2003, 10:25 AM
I also get the same messages...
[Wed Dec 17 12:24:38 2003] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux) PHP/4.3.0 configured -- resuming normal operations
[Wed Dec 17 12:24:38 2003] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Wed Dec 17 12:24:42 2003] [warn] (95)Operation not supported: setsockopt: (TCP_NODELAY)
Hopefully soon someone will let us know!

wildjokerdesign
12-18-2003, 12:40 PM
Not sure on this but when they first moved to 2.0 there where some problems with the relaying on e-mail and some other things. I think part of it had to do with how long the system "remembered" you when checking your mail. At that time WestHost did make a change that made it last for 24 hours. I wonder if this has something to do with it.

That may not be what is happening but almost sure it is something WestHost is doing every 24hrs. If I am not mistaken they do make backups but not sure how often that happens.

jalal
12-18-2003, 12:51 PM
I asked them about this (although my errors were slightly different, something with "SIGTERM") and they said that Apache will shut down to conserve resources if not used for a while.

So, if a site is busy, you will never see the error, other sites with only occasional visitors will get the error regularly.

wildjokerdesign
12-18-2003, 01:37 PM
Boy I was way off on that one. :)

firebirdfan
12-18-2003, 05:55 PM
I also got a reply stating that "its normal" ...but thanks for the clearer picture of what's happening :)