Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I have a problem with my computer restarting seemingly at random. From lots of grepping, it seems the computer tends to restart while in use, but just after syslogd has restarted (i.e. in the same second each time). However, a restart does not follow every syslogd restart.
I know this sounds awfully like a hardware complaint, but I was wondering if anyone could shed any light on the syslogd/restarting possible connection.
Syslogd is usually scheduled to restart around the same time as several high I/O bandwidth activities (like prelink and updatedb). I had a machine with exactly the same problem. It turned out to be a flaky firewire card with an external HD. When the I/O rate got high, the machine reset (usually at 4am). I was able to recreate the problem by rsyncing a large (1GB) file from the internal drive to the external drive. After swapping the firewire card for another, the problem ceased.
Another thing to consider is the power supply. When all the drives are busy, they also draw the most current. If you are running your PS near its limit, that could also cause a glitch/reset.
My friend had a laser printer plugged into the same outlet as the PC. When she powered up the laser printer, the PC reset. Are there any high-current devices on the same circuit as the PC that could spike the voltage?
Power was what it came down to in the end, yes. I had two computers plugged into the same socket, and that is what seemed to have done it. I have now put it in an exclusive socket, and the computer has happily stayed on since.
Thanks for the response, it's interesting what clues linux can give you sometime, isn't it...