Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
I have a debian (wheezy) web server (home built machine) that frequently (once a day) goes offline mysteriously. I administer the server via ssh and when it goes offline a "Broken pipe"g message appears, which means that the SSH connection died. Websites are no longer reachable. If I connect a monitor to the webserver after the server is unreachable by SSH and sites unreachable, the monitor screen remains black (entire system is dead?). The only thing I can do is a force reboot via the power button. Many times it takes two reboots for the server to become reachable again.
I have reviewed /var/log files and searched and have come up empty on a possible the cause.
When this happens, I notice that /var/log/syslog file reports one or more tables in a mysql database has crashed and needs repair. However, repairing the database tables via myphpadmin does not prevent the server from going offline again, which may indicate the database table crash was due to the force reboots.
I have checked the server for rootkts with rkhunter (1.4.0) and none are found.
I can post only 2 minutes of the syslog file and doubtful it will be very informative.
Any suggestion on what to look for in my log files or any kind of pointer will be appreciated.
I noticed that postfix was not running, so I started the postfix service. Since starting postfix, the problem appears to have disappeared. I say disappeared because I feel like I have not done enough to know the absence of postfix was causing the problem. The system has been running for the past 30 or so hours, which is significantly longer than the 1 hr or less that was happening.
For now, I will call this problem apparently solved.
This is just a follow up post with the final solution that was causing the problem described in the first post of this thread. The root cause was heat, which was due to a faulty power supply. The symptoms described above has gone away after replacing the power supply. The system has been running for over a week without issue.
Thanks tux111 and leandean for replying. The replies helped pave the way to a resolution.
Last edited by drhood; 11-04-2013 at 05:17 AM.
Reason: Added specificity