Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Instantly restart a server or workstation each day' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Instantly restart a server or workstation each day
Authored by: mickazoid on Oct 17, '05 10:32:34PM
I found myself considering a daily restart when I found services on my main web/mysql production server Mac were becoming more and more unresponsive under heavy use (this was in the era of Jaguar). The delays and timeouts would grow so problematic, I considered and wrote a similar crontab.

However, I luckily wound up not needing to do so - I found a correction to my particular demon "bug-du-jour".

Your machine wants to be a high-uptime machine. It doesn't want to be rebooted every day. And you don't wanna do that to your nice server, do you?

I wish you all the best luck in finding, and eradicating, the bug - or simehow finding a means to avoid the bug's error condition until an appropriate Apple update is released.

[ Reply to This | # ]

Instantly restart a server or workstation each day
Authored by: stewarsh on Oct 17, '05 10:49:44PM

What, if I may ask, did you do? We are seeing problems with python slowing on one of our other XServe webservers.



[ Reply to This | # ]
Instantly restart a server or workstation each day
Authored by: mickazoid on Oct 17, '05 11:14:44PM
Well, in a nutshell, we first installed a vanilla setup from scratch on an all-new machine (to find any specific bugaboos that might have accompanied this box config in particular. Always a good idea. Then when we found the problem was indeed replicable across vanilla installs, we made intimate use of the apache server, mysql and server monitoring capabilities (as you did) to watch individual web and server process threads in action. Then we'd recompile the various code modules for each of the relevant web, app and db products in use. When we found a combination that consistently threw errors, we recompiled the related code to test for incremental exceptions until we trapped the condition.

Sorry to be vague but that's the most consise way to describe it :)

[ Reply to This | # ]