LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 02-22-2010, 05:44 AM   #1
hadimotamedi
Member
 
Registered: Aug 2009
Posts: 228

Rep: Reputation: 30
/var/log/messages(dmesg) ?‏


Dear All
My Debian server got hung and when I tried to power cycle it , I checked its /var/log/messages & /var/log/dmesg with respect to the time of fault occurance to see what was really happened . But its 'messages' log does not show anything recorded for about 30 minutes before its recovery after power cycling . Can you please let me know where I can check to find the root cause of failure ?
Thank you
 
Old 02-22-2010, 06:46 AM   #2
evo2
LQ Guru
 
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and Scientific Linux
Posts: 5,753

Rep: Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288
Sometimes hardware failures will occur in such a way that nothing will/can be written to the log files. Also, when you reboot, the time stamps on the log files will be updated which can make it difficult to work out what was the last thing written before the crash. One thing you can do after such a lock up is boot to a live/rescue cd, and then mount the file system read only: this should make it easier to see what was going on just before the crash.

Cheers,

Evo2.
 
Old 02-22-2010, 07:00 AM   #3
hadimotamedi
Member
 
Registered: Aug 2009
Posts: 228

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by evo2 View Post
Sometimes hardware failures will occur in such a way that nothing will/can be written to the log files. Also, when you reboot, the time stamps on the log files will be updated which can make it difficult to work out what was the last thing written before the crash. One thing you can do after such a lock up is boot to a live/rescue cd, and then mount the file system read only: this should make it easier to see what was going on just before the crash.

Cheers,

Evo2.
Thank you for your reply . Can you please provide more details on this procedure ? After booting from /rescue mode and mounting the file system read only , where I can check for what was going on before the crash ?
 
Old 02-22-2010, 07:30 AM   #4
evo2
LQ Guru
 
Registered: Jan 2009
Location: Japan
Distribution: Mostly Debian and Scientific Linux
Posts: 5,753

Rep: Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288Reputation: 1288
Start with the files in /var/log/ you may be able to find something that you would otherwise overlook if the machine had booted up again normally. Another place to look in is /tmp/, which will normally be completely deleted on a reboot.

Cheers,

Evo2.
 
Old 02-22-2010, 08:33 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,604
Blog Entries: 25

Rep: Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981Reputation: 1981
Hi,

You could try a another console while the system is still up. Meaning try to login via another console then look at the system messages or information to diagnose without re-booting. Or attempt to login via 'ssh' to console then look at the system conditions.

 
Old 02-23-2010, 12:06 AM   #6
hadimotamedi
Member
 
Registered: Aug 2009
Posts: 228

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by onebuck View Post
Hi,

You could try a another console while the system is still up. Meaning try to login via another console then look at the system messages or information to diagnose without re-booting. Or attempt to login via 'ssh' to console then look at the system conditions.


Thank you . But my Red Hat server hard drive LED was continously lit and no login was possible on any console/SSH session . I want to find why this is occured .
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
use of /var/log/dmesg File krajkum Linux - Server 1 03-04-2009 10:57 AM
/var/log/messages and /var/log/cron not working sigkill Linux - Software 6 08-09-2008 02:08 PM
dmesg (command) and /var/log/dmesg are different? Oxagast Linux - Software 2 07-10-2006 06:50 AM
/var/log/messages is empty, and also dmesg shows nothing beagle2 Linux - General 5 11-08-2005 09:12 AM
Boot messages not the same as "dmesg" or "/var/log/messages"? massai Linux - General 5 03-10-2004 01:18 AM


All times are GMT -5. The time now is 09:04 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration