From: Randy Millis (lists account) (rmillisl@gdcanada.com)
Date: Mon Nov 28 2005 - 13:37:38 EST
> A kill -KILL is essentially taking a shotgun to the process; rather than
asking the process to die nicely; the kernel steps in and swats it. A
program cannot refuse to process a KILL signal, unless it runs in kernel
space.
My other kill attepts failed as well.
> So if a process is not defunct (i.e. there is no process to process the
signal) and it isn't responding to a kill -KILL then it is blocking in the
kernel. This is *usually* blocking on hardware (though it can block on other
things - e.g. NFS can block like this as NFS runs in the kernel). It may
also mean it's blocking on IPC (e.g. semaphores)
I understand better now. Thanks.
Side note: No NFS running here.
> If you have glance, check for why it's blocking and what it's blocking on;
this may indicate where the deadlock is.
> If you don't have glance then you're a bit blind.
No glace license. :-(
> First thing I'd do would be to kill the client off as far as you can -
cleanly first (e.g. through /sbin/init.d) and hard if you can't. Then clean
up and semaphores that are open (IPCS) - glance is useful for this. Again,
if you have glance, you can look at what files are open and deal with these
(lsof, if installed, can also do this).
No kill attempts seemed to work. Only rebooting.
> Check /var/adm/syslog/syslog.log and dmesg for any obvious errors with
hardware or other kernel messages (dmesg may be the most useful here)
Nothign I can see in either that appear hardware related.
> These sorts of problems are the worst to solve and usually the quickest
way is to bounce the box - though this is drastic!
Trouble is it keeps coming back.:-(
The information contained in this e-mail message is PRIVATE. It may contain confidential information and may be legally privileged. It is intended for the exclusive use of the addressee(s). If you are not the intended recipient, you are hereby notified that any dissemination, distribution or reproduction of this communication is strictly prohibited. If the intended recipient(s) cannot be reached or if a transmission problem has occurred, please notify the sender immediately by return e-mail and destroy all copies of this message.
Thank you.
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:50 EDT