Quoting Bob Miller <[EMAIL PROTECTED]>:
> [EMAIL PROTECTED] wrote:
>
> > I have a process that cannot be killed by 'kill -9 PID'
>
> You're screwed. You're going to have to reboot.
>
> But before you do, there is some more info you can collect.
>
..
>
> Second, what is the process blocked on? I don't have access to a
> Solaris system, but most Unices have a ps option that displays the
> WCHAN field.
Thanks Bob -- twas an interesting exercise:
ps -ef -o ppid,pid,wchan,args | grep apach > bad-pid
inspect bad-pid, then
ps -ef -o ppid,pid,wchan,args | grep 61992b66
only showed the bad apple and the grep itself
from Garl:
>> "Where is the binary for this 'immortal' process? "...
Thanks Garl -- it all happend on locally mounted drives.
The bad process was originally apache listening on port 80 (screwed up via
mod_fastcgi and a bad cgi script)
Interestingly
'ls -l /proc/2131/' # bad, old httpd:80
still looks quiet similar to
'ls -l /proc/14326/' # now running httpd:8080
But that's about as deep as I want to go into /proc/ until I exactly know what I
am doing.
I think I have to wait for Sunday to reboot...
- Horst
_______________________________________________
EuG-LUG mailing list
[EMAIL PROTECTED]
http://mailman.efn.org/cgi-bin/listinfo/eug-lug
