kill -9 doesnot work

[Kaushal Shriyan]

Hi ALL

kill -9 doesnot work

[root@e guptavi]# ps -eaf | grep bdc
root      3218  3126  0 17:28 ?        00:00:00 ./bdc_switcher an -n
an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
22001 -vvvvvvvv
root      4240  4191  0 18:01 pts/1    00:00:00 grep bdc
[root@e guptavi]#  kill -9 3218 3126
[root@e guptavi]#
[root@e guptavi]# ps -eaf | grep bdc
root      3218     1  0 17:28 ?        00:00:00 ./bdc_switcher an -n
an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
22001 -vvvvvvvv
root      4243  4191  0 18:01 pts/1    00:00:00 grep bdc

Any clue

Thanks and Regards

Kaushal

[Rodolfo Alcazar Portillo]

On Wed, 2006-08-02 at 18:08 +0530, Kaushal Shriyan wrote:
>  Hi ALL
>  
>  kill -9 doesnot work 
Yep. Does not always work. AFAIK, mostly happens when the kernel expects
for a hardware signal. There are some other causes, also. Try finding
the problem, instead of killing it!

>  [root@e guptavi]# ps -eaf | grep bdc
>  root      3218  3126  0 17:28 ?        00:00:00 ./bdc_switcher an -n
>  an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
>  22001 -vvvvvvvv
>  root      4240  4191  0 18:01 pts/1    00:00:00 grep bdc
>  [root@e guptavi]#  kill -9 3218 3126
>  [root@e guptavi]#
>  [root@e guptavi]# ps -eaf | grep bdc
>  root      3218     1  0 17:28 ?        00:00:00 ./bdc_switcher an -n
>  an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
>  22001 -vvvvvvvv
>  root      4243  4191  0 18:01 pts/1    00:00:00 grep bdc
>  
>  Any clue
>  
>  Thanks and Regards
>  
>  Kaushal
>   
-- 
Rodolfo Alcazar
Administrador datos y red

Deutsche Gesellschaft für
Technische Zusammenarbeit (GTZ) GmbH

Programa de Apoyo a la Gestión Pública Descentralizada y 
Lucha Contra La Pobreza - PADEP

Av. Sánchez Lima 2226
T [phone] (121)
C [phone]
E rodolfo.alcazar(a)padep.org.bo
I www.padep.org.bo

[Andrew Parker]

On 8/2/06, Rodolfo Alcazar <rodolfo.alcazar(a)padep.org.bo&gt; wrote:
>  On Wed, 2006-08-02 at 18:08 +0530, Kaushal Shriyan wrote:
>  > Hi ALL
>  >
>  > kill -9 doesnot work
>
>  Yep. Does not always work. AFAIK, mostly happens when the kernel expects
>  for a hardware signal. There are some other causes, also. Try finding
>  the problem, instead of killing it!
>  
indeed.

strace on the process will tell you the last kernel function called
and may give clues as to where the problem lies.

[Rick Stevens]

On Wed, 2006-08-02 at 09:03 -0400, Rodolfo Alcazar wrote:
>  On Wed, 2006-08-02 at 18:08 +0530, Kaushal Shriyan wrote:
>  > Hi ALL
>  > 
>  > kill -9 doesnot work
>  
>  Yep. Does not always work. AFAIK, mostly happens when the kernel expects
>  for a hardware signal. There are some other causes, also. Try finding
>  the problem, instead of killing it! 
"kill -9" will not work for processes in a "D" state (I/O wait
state),
for example.  If said processes receive their I/O interrupt, they
should recognize the signal and die.

"kill" will also not kill zombies ("Z" state).  You must kill their
parent processes first and the zombies will disappear of their own
accord.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens(a)vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-                   Never try to outstubborn a cat.                  -
----------------------------------------------------------------------

[Matthew Miller]

On Wed, Aug 02, 2006 at 11:32:56AM -0700, Rick Stevens wrote:
>  "kill" will also not kill zombies ("Z" state). 
> You must kill their
>  parent processes first and the zombies will disappear of their own
>  accord. 
Because, of course, the zombies are already dead -- there's no process
there, just a process ID that hasn't been released.

-- 
Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
Boston University Linux      ------>              <http://linux.bu.edu/>

[Kaushal Shriyan]

On 8/3/06, Matthew Miller <mattdm(a)mattdm.org&gt; wrote:
>  On Wed, Aug 02, 2006 at 11:32:56AM -0700, Rick Stevens wrote:
>  > "kill" will also not kill zombies ("Z" state).  You must kill
> their
>  > parent processes first and the zombies will disappear of their own
>  > accord.
>
>  Because, of course, the zombies are already dead -- there's no process
>  there, just a process ID that hasn't been released.
>
>  --
>  Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
>  Boston University Linux      ------>              <http://linux.bu.edu/>
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  

Hi ALL

I got to know the root cause of the kill -9 command

ls command hangs

in nfs mounted partition tnfs-dev.test.example.com:/config 140G  135G
5.1G  97% /config where my process is looking for some files.

Is there a way to fix it?

Please let me know if you need more info on this

Thanks and Regards

Kaushal

[Matthew Miller]

On Thu, Aug 03, 2006 at 11:43:36AM +0530, Kaushal Shriyan wrote:
>  in nfs mounted partition tnfs-dev.test.example.com:/config 140G 
> 135G
>  5.1G  97% /config where my process is looking for some files.
>  Is there a way to fix it? 
Mount the nfs partition so that it's interruptible.

-- 
Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
Boston University Linux      ------>              <http://linux.bu.edu/>

[Kaushal Shriyan]

On 8/3/06, Matthew Miller <mattdm(a)mattdm.org&gt; wrote:
>  On Thu, Aug 03, 2006 at 11:43:36AM +0530, Kaushal Shriyan wrote:
>  > in nfs mounted partition tnfs-dev.test.example.com:/config 140G  135G
>  > 5.1G  97% /config where my process is looking for some files.
>  > Is there a way to fix it?
>
>  Mount the nfs partition so that it's interruptible.
>
>  --
>  Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
>  Boston University Linux      ------>              <http://linux.bu.edu/>
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  
Hi Matthew

Its mounted in /etc/mtab

tnfs-dev.test.example.com:/config /config nfs rw,addr=172.18.216.167 0 0
aolbdcaf01.office.aol.com:/vol/data/home/guptavi /u/guptavi nfs
rw,nosuid,addr=10.16.14.60 0 0

Thanks

Kaushal

[Matthew Miller]

>  On 8/3/06, Matthew Miller <mattdm(a)mattdm.org&gt; wrote:
>  >> in nfs mounted partition tnfs-dev.test.example.com:/config 140G  135G
>  >> 5.1G  97% /config where my process is looking for some files.
>  >> Is there a way to fix it?
>  >Mount the nfs partition so that it's interruptible.
>  Its mounted in /etc/mtab 
mtab just shows what partitions are mounted; it's not where it's mounted
*from*. To be able to kill things that are timing out in NFS, you want to
either mount the filesystem 'soft' or 'intr'.

-- 
Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
Boston University Linux      ------>              <http://linux.bu.edu/>

[Kaushal Shriyan]

On 8/3/06, Matthew Miller <mattdm(a)mattdm.org&gt; wrote:
>  > On 8/3/06, Matthew Miller <mattdm(a)mattdm.org&gt; wrote:
>  > >> in nfs mounted partition tnfs-dev.test.example.com:/config 140G  135G
>  > >> 5.1G  97% /config where my process is looking for some files.
>  > >> Is there a way to fix it?
>  > >Mount the nfs partition so that it's interruptible.
>  > Its mounted in /etc/mtab
>
>  mtab just shows what partitions are mounted; it's not where it's mounted
>  *from*. To be able to kill things that are timing out in NFS, you want to
>  either mount the filesystem 'soft' or 'intr'.
>
>  --
>  Matthew Miller           mattdm(a)mattdm.org          <http://mattdm.org/>
>  Boston University Linux      ------>              <http://linux.bu.edu/>
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  
Hi Matthew

I went through
http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/ref-guide/s1-nfs-...

Thanks

Kaushal

[Andrew Parker]

On 8/2/06, Kaushal Shriyan <kaushalshriyan(a)gmail.com&gt; wrote:
>  Hi ALL
>
>  kill -9 doesnot work
>  
Its probably stuck in a system call and is waiting for the kernel to
complete an operation.  This is often because of a remote file system
that is misbehaving/down and the kernel is waiting for a response it
is never going to get.  if you run df and that hangs, its definately a
remote file system.  cat /etc/mtab to see which file system it is
(usually the next fs after the last one df displayed).

[Brian Chadwick]

gb spam wrote:
>  On 8/2/06, Kaushal Shriyan <kaushalshriyan(a)gmail.com&gt; wrote:
> > Hi ALL
> >
> > kill -9 doesnot work
> >
>
>  Its probably stuck in a system call and is waiting for the kernel to
>  complete an operation.  This is often because of a remote file system
>  that is misbehaving/down and the kernel is waiting for a response it
>  is never going to get.  if you run df and that hangs, its definately a
>  remote file system.  cat /etc/mtab to see which file system it is
>  (usually the next fs after the last one df displayed).
>  
i have found this behaviour myself ... and not using remote file systems 
... some things do just ... it seems ... die ... and the kernel cant rid 
itself of them ... win4lin modules are a classic case of this ...

[Robin Laing]

Kaushal Shriyan wrote:
>  Hi ALL
>  
>  kill -9 doesnot work
>  
>  [root@e guptavi]# ps -eaf | grep bdc
>  root      3218  3126  0 17:28 ?        00:00:00 ./bdc_switcher an -n
>  an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
>  22001 -vvvvvvvv
>  root      4240  4191  0 18:01 pts/1    00:00:00 grep bdc
>  [root@e guptavi]#  kill -9 3218 3126
>  [root@e guptavi]#
>  [root@e guptavi]# ps -eaf | grep bdc
>  root      3218     1  0 17:28 ?        00:00:00 ./bdc_switcher an -n
>  an_adb_switcher-d01 -b adb_switcherpre.tcl -a adb_switcherpost.tcl -p
>  22001 -vvvvvvvv
>  root      4243  4191  0 18:01 pts/1    00:00:00 grep bdc
>  
>  Any clue
>  
>  Thanks and Regards
>  
>  Kaushal
>   
If the process is waiting for something else to end, it could take some 
time to die.  I ran into this the other day while trying to do something 
with a DVD drive that was acting up.

That is the only thing that I can think of.

-- 
Robin Laing