Linux - NewbieThis 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
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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
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.
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 ?
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.
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.
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 .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.