topic unable to kill process with PPID 1 in Operating System - HP-UX

unable to kill process with PPID 1

ani007 — Fri, 18 Feb 2011 08:56:56 GMT

Hi,
In my production server we are not able to kill one process as PPID become 1.I am sending you one attachment of list of process running... except reboot is there any other waay to kill it. kill -9 not worked.

Re: unable to kill process with PPID 1

Jose Mosquera — Fri, 18 Feb 2011 09:14:25 GMT

Hi,

The "kill -9 19057" syntax should work. Likely to take time for the tape drive (sequential operation) returns control to the system.

PID = 1 is the **master** (init) process of your server, please do not try to attack him!

Rgds.

Re: unable to kill process with PPID 1

ani007 — Fri, 18 Feb 2011 09:24:03 GMT

HI,
The process is there from 6th feb.this is the current status of tape drive..

Drive: HP C7438A
Format:
Status: [41112600] BOT online compression immediate-report-mode
File: 0
Block: 0

shall we try to power cycle the drive?
REagrds,
Ani

Re: unable to kill process with PPID 1

Jose Mosquera — Fri, 18 Feb 2011 09:37:44 GMT

Is the tape in the drive yet?
Does the tape activity (ie: flashing lights)?
Is the drive CLAIMED by the system?
#ioscan-fnCtape

Re: unable to kill process with PPID 1

Matti_Kurkela — Fri, 18 Feb 2011 09:42:25 GMT

The fact that PPID is 1 is probably not related to being unable to kill the process: it just means that the original parent process has already died, and the orphaned process has been adopted by init (process #1).

If kill -9 does not kill a process immediately, that often means the process is waiting for some kernel-level operation to complete (for example, SCSI I/O). If the kill -9 signal is already sent, the kernel will process the signal as soon as the operation completes.

But if the kernel-level operation will not reach completion at all (perhaps because some hardware has failed, or a cable has been disconnected accidentally), then an unkillable process will result.

My suggestion:
Check the "dmesg" output, the system log and the STM diagnostics for any indications of hardware failure (SCSI error/lbolt messages, other errors). If you find hardware problems, fix them first: they might be the root cause for your unkillable processes.

If all the hardware is OK, the next thing to check would be your patch levels.

MK

Re: unable to kill process with PPID 1

ani007 — Fri, 18 Feb 2011 09:45:15 GMT

as i am working remotely so i try to rewind & prompt return.

# mt -t /dev/rmt/XXmn rew
#
so i think tape is there.
yes i hv seen it is clamed in ioscan

Drive: HP C7438A
Format:
Status: [41112600] BOT online compression immediate-report-mode
File: 0
Block: 0
======================
Status: [41112600] BOT online compression immediate-report-mode -- so drive is online right..
So i think reboot is only option..

Regards,
Ani

Re: unable to kill process with PPID 1

Jose Mosquera — Fri, 18 Feb 2011 09:56:13 GMT

You are in remote... Anyone can be your eyes on the remote location?
Try to eject the tape with:
# mt-t / dev/rmt/20mn offl

In addition to Matty's suggestions, please check if the file syslog.log have any warning from the EMS?

Re: unable to kill process with PPID 1

ani007 — Fri, 18 Feb 2011 10:11:49 GMT

Thanks aa for your excellent support.I have cheked & no problem found.so we will take downtime & reboot.

Regards,
Ani

Re: unable to kill process with PPID 1

R.O. — Fri, 18 Feb 2011 10:12:22 GMT

Hi,

Have you checked if a vg00's disk is failing?

Regards,