Shane,
Based on your comment...
We have opened up problems with Novell and SAP. So far this has
happened on two of our Linux Guests. We crashed and booted one Monday
night. We crashed and booted the other one Tuesday night. (On the off
chance that it might help, last night I took a standalone dump of the
Linux guest in trouble. So far Novell has not wanted me to send the
dump to them.)
This morning, it looked like we had the same sort of problem happening
on a third Linux guest. That is we had a SAP dialog process that all
night. (We have the SAP parameters set to "time out" a dialog process
after a few minutes. The "timeout" did not work.) The DBAs cancelled
the DB2 thread. The SAP Administrators issued all the commands thru SAP
to get rid of the process. They did not work. The process did not go
away. Then we tried a kill -9 and the process died.
On the other two occassions, we issued the same commands. But they were
done independently by people in the different areas in different rooms.
This time everyone was in the same room waiting for the problem to happen...
Thanks for the insight,
Ron
Shane Ginnane wrote:
That is *UN*interruptible sleep.
Programming error , pure and simple.
And yes, it probably really is unkillable.
Shane ...
Ron wrote on 06/04/2010 08:41:15 AM:
I just had to #CP logoff on of our production SAP systems. It had a SAP
process on it with a process state of "D" interruptible sleep.
The sap cancel options would not work.
kill would not work.
kill -9 would not work on it.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
