Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an Ubuntu Godaddy server I use to host mail and webapps. It started having problems a couple months ago. It would lock up and stop responding to anything. I couldn't ssh into it, so I'd have godaddy power cycle the server.

I have never seen anything that looked suspicious in the var logs (although I'm no expert at reading them). An fsck turned up no problems. Godaddy replaced the ram, but found no hardware problems. I started logging the output from "top" to a log file and found that even that stops running when the server freezes.

Now, here is the crazy part: It got so bad that it would actually go down every few hours, but then it stopped going down. I eventually realized I had left an ssh terminal logged into the machine running top. This seemed unlikely to be a reason, but after the server was up with no problems for a full week (remember, it had been going down after just a few hours), I disconnected from the ssh session. Lo and behold, within a few hours the server froze again!

I had them power cycle again and then left another ssh session open with top. It has been going without problems for 8 days now.

I told others about this and they hardly believe me. I simply can't imagine what is going on. I don't know what else to try other than to just get a new server and reinstall everything.

Does anyone have any ideas about what I can look for to determine what the cause is? Is it possible there's some sort of exploit on the server which only runs if everyone is logged out of the system?

EDIT: The power management gone haywire sounds plausible, so I've modified the /boot/grub/menu.lst to boot with acpi=off and apm=off. It appears to have prevented kacpid and kacpid_notify from being in the process list, so I assume I did that right. I've disconnected all my sessions from the server. I'll check later tonight to see if it's still up. If it goes down then I'll try the pinging process idea.

EDIT: It went down again. It lasted about a day. I've had them reboot, so now I'll try running "nohup ping -i 5 google.com &" and then disconnect. If it goes down again I'll come back. Hopefully someone will have some more ideas.

EDIT: Huh. It hasn't gone down in 5 days. I have only briefly been logged in. The "nohup ping -i 5 google.com &" appears to do the job. Anyone have any ideas why? I'm not exactly excited about leaving my machine pinging google ever 5 seconds indefinitely, but if I can't figure out anything else I'll probably add a startup script that runs this when the server is rebooted.

share|improve this question
1  
What happens if you leave a process running, pinging another host periodically? That will keep the networking stack ticking over without leaving a network connection open. The idea here is to narrow things down by changing only some of the variables. Also, you could just try asking the hosting folks to move your disks to some entirely different hardware instance to see if the problem follows the hardware or follows the OS install. –  James Youngman Mar 22 '12 at 0:35
1  
This smells of a hardware problem. –  t1nt1n Mar 28 '12 at 20:00
    
I've had flaky hardware that did the same thing, ping "fixed" it just the same. Replacing the hardware with non-broken stuff worked better. –  Chris S Aug 20 '12 at 15:21
add comment

1 Answer

Some kind of power saving mechanism, going into sleep mode perhaps. Maybe disable the ACPI modules in /etc/modules.conf to test the hypothesis.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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