Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 14
I see a process running from 2 days. When I try to kill -9 it returns with no error but that process still keeps showing in top command. When I ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jun 2008
    Posts
    38

    Process not getting killed


    I see a process running from 2 days. When I try to kill -9 it returns with no error but that process still keeps showing in top command.

    When I do lsof I see somehting like:

    afaconv.l 5813 root txt REG 104,2 11396935 20021557 /home/afa_build/work/AFA/main/dist/deploy/jboss/server/afa/deploy/afa/afa-vert.rar/bin/afaconv.linux32 (deleted)
    afaconv.l 5813 root 0r FIFO 0,7 2523565 pipe
    afaconv.l 5813 root 1w FIFO 0,7 2523566 pipe
    afaconv.l 5813 root 2w FIFO 0,7 2523567 pipe
    afaconv.l 5813 root 3r REG 104,2 151307 21151952 /home/afa_build/work/AFA/main/dist/deploy/jboss/server/afa/deploy/afa/afa-vert.rar/form/wio03.1pe (deleted)

    I think it's in uninterruptible state but sounds like a very bad thing if it happens in our production servers. Any suggestions of what I should do?

  2. #2
    Linux Engineer khafa's Avatar
    Join Date
    Apr 2008
    Location
    Tokyo, Japan
    Posts
    858
    what is the process you want to kill and how does it show in top?
    maybe its a zombie
    Linux and me it's a love story

  3. #3
    Just Joined!
    Join Date
    Jul 2007
    Posts
    66
    Hi,

    Who is its parent process?

    --Kurian.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Engineer Thrillhouse's Avatar
    Join Date
    Jun 2006
    Location
    Arlington, VA, USA
    Posts
    1,377
    Quote Originally Posted by kurianthayil View Post
    Who is its parent process?
    I think Kurian is on the right track here. It's entirely possible that the parent process re-spawns the one you're trying to kill if it sees it go down. If that's the case, you'll have to kill the parent process.

  6. #5
    Just Joined!
    Join Date
    Jun 2008
    Posts
    38

    ps command

    As I mentioned that process has been running from 2 days. top output shows that. But, when I do "ps" it doesn't come up in the list.

  7. #6
    Linux Engineer Thrillhouse's Avatar
    Join Date
    Jun 2006
    Location
    Arlington, VA, USA
    Posts
    1,377
    A standard ps (with no parameters) will only show processes started or running for your currently logged in user. To show all processes (including kernel routines) use ps -Af. To show most system processes (not including kernel processes) use ps -ef.

  8. #7
    Just Joined!
    Join Date
    Jul 2007
    Posts
    66
    Hi,

    To show most system processes (not including kernel processes) use ps -ef.
    As Thrillhouse has said use ps with -ef option. PID could be obtained from the top command and then use ps -ef to find out its details.

    #ps -ef |grep <processid from top>

    --Kurian.

  9. #8
    Just Joined!
    Join Date
    Jun 2008
    Posts
    38

    Angry ps

    I have already tried the following:

    top and then kill -9 <pid> # from top
    ps -ef|grep "<pid>"
    ps -ef|grep "<process name"

    Since this program is not Kernel routine it will not appear in ps -Af.

    So going back to my real question. Why is kill -9 not able to kill the process that appears in top. The same process doesn't appear in ps -ef or ps -eaf or ps -Af

  10. #9
    Just Joined!
    Join Date
    Jul 2007
    Posts
    66
    Hi,

    Were you able to trace its parent process??? The child process would be re-spawned by the parent so if the parent is not killed it will still spawn child even if you kill the child. Suppose if 6750 is the PID that's making problem (Child) and If you need to find its parent, do the command.

    Code:
    #ps -ef |grep 6750
    kurianmt  6750  6749  0 06:34 ?        00:00:00 /bin/sh /opt/glib2.16/firefox3/firefox
    kurianmt  6857  6790  0 06:36 pts/0    00:00:00 grep 6750
    The parent of the child process 6750, is 6749. So killing the PID 6749 will kill its child too. You will have to trace like that. Make sure you won't kill PID 1. Hope you are aware of that.

    --Kurian.

  11. #10
    Just Joined!
    Join Date
    Jun 2008
    Posts
    38

    ps

    That's not the issue. There is no parent process trying to spawn child process. As I mentioned earlier, this process has entered in a state that doesn't appear in ps but is seen in top. Which means that it's not getting respawned because the PID in top output is same. Also I already mentioned that this process is running over 2 days, as reported by top. So it can't be a parent re-spawning child. Does somebody else has any more information about why process would enter such a state?

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •