0

My server is restarted by itself tonight. How can I determine waht caused this? I checked in /var/log/messages but I can't understand from there.

Is there any other way/option ?

I use Red Hat Enterprise Linux AS release 3 (Taroon Update 5)

Thanks

Improve this question
  • All other issues aside, RHEL is now well past end-of-life, and as a result any number of exploitable situations might arise. You are aware of this, yes? – MadHatter Oct 11 '12 at 7:51
  • Sorry, but I don't understand what you trying to say ? I don't decide on my own what distribution to use.. – Jason Paddle Oct 11 '12 at 7:54
  • 1
    Your server is past end-of-life on the OS. If there were, say, remotely-exploitable bugs which could be used to trigger remote reboots, they won't be patched by Red Hat. If you think there might be a problem with this server, getting it onto an up-to-date version of the OS (RHEL 5, or better, 6; or if budget is an issue, CentOS 6) is pretty much a first step, if the availability of this server is important to you. – MadHatter Oct 11 '12 at 7:56
  • 1
    I don't want to appear catty, but you don't know where the problem is, or you wouldn't be asking here. If you're looking for a minefield, it's important not to drive past the big signs on the right saying "MINEFIELD" just because you're sure the field is over to the left. – MadHatter Oct 11 '12 at 8:05
  • 1
    I have some servers like that. The HA pairs fail every 497 days because they're running a really old Linux where the uptime clock resets every 497 days or so, and that causes the HA logic to fail hard, so every box tries to be primary at the same time. My point is that once bugs are no longer being fixed, the oddest things can cause systems to fail, and finding out why can be very painful and time-consuming; in my case, it took about three years to work out what was happening. I hope you get lucky. – MadHatter Oct 11 '12 at 8:30
2

Best guess:

Your server is restarting because some piece of hardware in it is failing. It is, after all, an antique that should have been decommissioned years ago. The symptom you describe is also strongly correlated with failed hardware components, regardless of the age of the system.

Improve this answer
  • Acording to alarms all components are healthy and runing normaly.But probably is some device is failed. Other co-worker investigate this now. – Jason Paddle Oct 12 '12 at 13:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.