On Fri, 26 Mar 2004 02:07:12 +0530, "Devdas Bhagat" <[EMAIL PROTECTED]> said:
> Wrong attitude. You need to figure out the root cause of the problem, > and then make sure it does not happen again. yes, I know. But with a live server, I cant wait for the root cause. What I needed was an immediate fix. Then only I will go for the cause of the prblem. > Sure sounds like a cron issue to me. Lets see, at 4 am, I have updatedb > and the log analysers running. Either one of those could have been the > cause of the reboot, or maybe just the two together overloaded the box, > and had it get OOM. Or hit a bad segment of memory and caused an oops. > > But you have not found the problem at all :) > > Devdas Bhagat I know what cron is, what updatedb is and what they have got to do with system load. We had been monitoring the server for almost one week with it set to mail us with w, ps aux, top three lines from top, free memory and all every minute during the time from 3:30am to 4:30 am, server time. The server was at Rackshack (DataCenter) and the rackshack techs were also not able to find anything wrong with the server. And in that case, the server was not going down exactly at the same time.. somewhere around 4:00 am.. but not much deviating. Its not the load, its not the memory problem, we knew that much :-\ -- Jemshad O K http://jemshad.com System Administrator Deru Communications http//deru.net @(-_-)@ "I know Karate, Kung Fu, and 47 other dangerous words" -- http://www.fastmail.fm - Does exactly what it says on the tin ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
