Unable to kill this process, Pls help!!

[rveri]

Hi All ,

I am unable to kill this process , pls help.
Tried # kill -15 and kill -9 , but the pid gets changed after using kill -9 , and it does not gets killed.

-----------------------------------------
root 29604 1 0 Feb 16 ? 0:00 /opt/ignite/lbin/list_expander -s -S -f /var/opt/ignite/recover
------------------------------------------

This left after interupting make_tape_recovery process. And trying to rerun , but this is already exists hence make_tape_recovery is failing. Please suggest to kill this process.

Thanks in advance.

[Pete Randall]

It's obviously being respawned when killed. Your only hope is to kill the process that is respawning it or reboot.


Pete

[Raj D.]

Seems you have very less option as the parent process is pid=1 , i.e init.

cheers,
Raj,

[Peter Godron]

Hi,
the example you show is Feb 16th.
If you kill that process what was the value in the 3rd column. If it not 1, do a
ps -ef | grep x where x is the 3rd column.
That should give you the parent/spawning process, which you can then kill.

Please try
kill 1
kill 2
kill 15 first

[Carlos Roberto Schimidt]

Hi

Try use lsof for identify all file descriptors for the process.

# lsof -p 29604

If you have some files, try identify if others process access the same file.

[rveri]

Thx all ,

Peter the 3rd field remains same after killing , its remains 1 only. And surely that is init process.

i dont want to reboot as of now:

Is there any trick
1. to kill this process.
2.or to remove from the process table.
3. or to rerun make_tape_recovery bypassing this sub command of make_tape_recovery.

What experts says!

[DCE]

It is probably being respawned by another Ignite process. Shutting down or killing all the ignite processes MAY take of the issue.

[Arunvijai_4]

Hello,

You can try killing both the processes and check .. It could be because of respawning

-Arun

[rveri]

There only one process. And nothing else to kill.

Thank you.

[Patrick Wallek]

Do you see anything else if you do a

# ps -ef |grep ignite

Also check the /etc/inittab and see if there is anything in there about this list_expander process.

[Andrew Merritt_2]

The date of the process is Feb 16, so unless it's an old listing, I don't think it is being respawned. When you say 'the pid gets changed', which number in the 'ps' listing do you mean? Is it the PID or the PPID?

The parent process id is '1', or the init process, so there is no parent to kill, according to the listing you've included.

If that's the case, then there's nothing you can do to remove the process short of rebooting. It is most likely that the process is hung in kernel space, and you can't do a lot about it. It's probably waiting for a system resource. A kernel knowledgeable person might be able to give instructions on how to narrow down what the exact call is that it is inside of, or you could call HP support for assistance.

Andrew

[Carsten Krege]

Often enough a look on the priority of a process tells you if it is signable (=killable) or not. Timeshare processes with priorities between 128 and 153 are not killable, usually because they are blocked on some kernel activity (like waiting for I/O).

See /usr/include/sys/param.h. Search for PZERO.

Carsten