Link to home
Start Free TrialLog in
Avatar of rstaveley
rstaveleyFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Killed processes in state D - uninterruptible sleep (usually IO)

I've just killed a daemon with SIGTERM and then after a few minutes of no response killed it again brutally with SIGKILL. I can see its thread in my `ps x` listing all with in state D, which my man page tells me is uninterruptible sleep (usually IO). The daemon is home-grown, and has been well behaved for the last few months.

Any suggestions what I should be looking at to get to the bottom of the problem?
ASKER CERTIFIED SOLUTION
Avatar of bobgunzel
bobgunzel

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of rstaveley

ASKER

It is a standard kernel and standard hardware (+drivers). I guess I should just wait and see if it happens again.
> dmesg

After the reboot? It has already been rebooted. Are the messages from the previous boot preserved?
sometimes /var/log/dmesg
I'm none the wiser from /var/log/messages. I'll just have to see if it happens again. Thanks for the help, chaps.