Server hung but could not locate the error in logs

[tomcatf14]

Hi,

My DA has been dying on me once in few weeks. On the most recent case, I managed to view the error on the console but unable to capture it.

After a reboot, I can't find back the error on the console on any of the logs. Can anybody let me know where is the console logs being saved in?

The error on the console look something like this:

php-cgi 120 execution hung xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

 

[nobaloney]

Is DirectAdmin itself dying? Or a specific website?

Jeff

 

[tomcatf14]

The whole server was inaccessible but pingable

 

[nobaloney]

That's most likely NOT a DirectAdmin issue. When that happens you should arrange a power-reboot of the server. Then you can start searching lots to see if the server was especially busy, or if processes had hung and couldn't be restarted.

Jeff

 

[tomcatf14]

That's most likely NOT a DirectAdmin issue. When that happens you should arrange a power-reboot of the server. Then you can start searching lots to see if the server was especially busy, or if processes had hung and couldn't be restarted.

Jeff

Hi Jeff,

How do I "start searching lots"?

 

[nobaloney]

I didn't mean lots; I meant logs.

Jeff

 

[tomcatf14]

I didn't mean lots; I meant logs.

Jeff

Which logs would you usually check on to troubleshoot the server hang problem?

 

[nobaloney]

Any/all of them that have entries around the time the server hung.

Jeff

 

[scsi]

Its more then likely a hardware problem. I would ask the datacenter for a hardware swap.

 

[nobaloney]

Its more then likely a hardware problem. I would ask the datacenter for a hardware swap.

It certainly could be a hardware problem. But in all the years I've run a datacenter I've never seen a simple hung server turn out to be a hardware problem. Every time in my memory it's been a process gone out of control.

Jeff