topic Re: Killing Hung Process. in Operating System - HP-UX

Killing Hung Process.

sdip — Tue, 21 Jun 2005 15:20:58 GMT

Hi,

I am unable to kill one of our hung process, the only option left to reboot the server. I was wondering if any solution left.

Please see the attached lsof output.
rr.scs 6097 aramadan cwd can't read cwd pst_filedetails: No such process

Is there any way to manage this situation.

Re: Killing Hung Process.

sdip — Tue, 21 Jun 2005 15:23:36 GMT

One more update.

Here is ps output...
aramadan 6097 1 0 01:20:23 ? 0:00

The OA version is 11i and server model is rp7410

Re: Killing Hung Process.

Olivier Masse — Tue, 21 Jun 2005 20:34:49 GMT

I think that most of the time, if kill -9 doesn't work and tusc can't attach to the process, it is hung in the kernel on an I/O request. It can be I/O on disk, network, NFS, etc.

It's hard to get rid of them without rebooting, unless the I/O gets magically satisfied. If it causes no harm, you can wait a few hours to see if it dies by itself.

Good luck

Re: Killing Hung Process.

Bill Hassell — Tue, 21 Jun 2005 22:35:19 GMT

HP-UX has no method to terminate a process that isn't running and that's exactly what a process is doint with I/O. Reboot and then rewrite the aapplication to test for uncompleted I/O.

Re: Killing Hung Process.

Abhijit_9 — Wed, 22 Jun 2005 03:30:56 GMT

Hello,

Those cases you need to reboot the system. No other option.

Regards,
Abhijit Roy

Re: Killing Hung Process.

Cem Tugrul — Wed, 22 Jun 2005 08:44:33 GMT

i am agree with Bill
Good luck,

Re: Killing Hung Process.

Jagadesh_2 — Fri, 24 Jun 2005 09:58:56 GMT

how to find the hung process?

Re: Killing Hung Process.

Bill Hassell — Fri, 24 Jun 2005 10:17:04 GMT

That is a symptom that you'll have to determine. Every process that does I/O (disk, network, tape, etc) is 'hung' during ther time that HP-UX is handling the task. Normally, this is just a fraction of a second. If you locate a process that is keeping a mountpoint busy and you know it's OK to kill this process, start with kill -15 and the process still exists (use ps -p ), then try kill -1 . If neither work, then the last resort is kill -9 . If that still leaves the process visible to ps -p, then the process is waiting on I/O that will never complete and there isn't any solution except to reboot.