Results 1 to 9 of 9

Thread: Kill unkillable task?

  1. #1
    Join Date
    Jul 2008
    Location
    Netherlands
    Posts
    1,140

    Default Kill unkillable task?

    On my server openSUSE 11.1 x86_64 KDE4.1 I got kacpi_notify taking up 50% of the cpu and zypper taking up 300MB of RAM which seems to be steadily growing..

    How do I kill these 2 as system monitor > Kill process doesn't do much besides asking for a root password.

    I'm reluctant to reboot as this will no doubt result in a disk error + 6 hour recovery process, for which I quite frankly don't have the time. Don't like the console view much either as the resolution isn't supported on the monitor on the server, but I can drag my normal one to it.
    Special effects <- KDE 4.2 Showing off
    More KDE -> PINK KDE

  2. #2
    Join Date
    Jan 2009
    Location
    PARADISE
    Posts
    929

    Default Re: Kill unkillable task?

    Quote Originally Posted by Axeia
    I'm reluctant to reboot as this will no doubt result in a disk error + 6 hour recovery process, for which I quite frankly don't have the time. Don't like the console view much either as the resolution isn't supported on the monitor on the server, but I can drag my normal one to it.
    First of all, I would fix this issue. Its not that good of an idea to let your PC run forever. SOME day, your computer will take the nap it always wanted...

    As for your personal problem:
    Quote Originally Posted by Axeia
    How do I kill these 2 as system monitor > Kill process doesn't do much besides asking for a root password.
    I would recommend you to press CTRL + ESC to call the process monitor. There you will be able to identify your tasks (as well as their PIDs), mark them and kill via the GUI.
    Now if that doesnt work, note down the PIDs and via console type:
    Code:
    kill YOUR-PID
    Hope it helps.

    TheMask.
    CHECK OUT THESE GitHub PROJECTS!

    https://secupwn.github.io/Android-IMSI-Catcher-Detector/
    https://github.com/SecUpwN/Spotify-AdKiller

  3. #3
    Join Date
    Jul 2008
    Location
    Netherlands
    Posts
    1,140

    Default Re: Kill unkillable task?

    Quote Originally Posted by TheMask View Post
    First of all, I would fix this issue. Its not that good of an idea to let your PC run forever. SOME day, your computer will take the nap it always wanted...
    As long as I'm in control of when it isn't too big a problem as I can plan it when I do have the time.
    Thread where I tried to narrow down the constant file corruption problem cause did not get me any satisfactory results so I'll just get a new harddrive, do a reinstall and see if that solves the problem, but till then I'd like to get rid of these tasks burning resources like there is no tomorrow.
    Quote Originally Posted by TheMask View Post
    I would recommend you to press CTRL + ESC to call the process monitor. There you will be able to identify your tasks (as well as their PIDs), mark them and kill via the GUI.
    Now if that doesnt work, note down the PIDs and via console type:
    That's the system monitor I refered to.

    Quote Originally Posted by TheMask View Post
    Code:
    kill YOUR-PID
    Same result as trying to do it trough the gui.
    Command execute fine, just doesn't do anything.
    Special effects <- KDE 4.2 Showing off
    More KDE -> PINK KDE

  4. #4
    Join Date
    Jan 2009
    Location
    PARADISE
    Posts
    929

    Default Re: Kill unkillable task?

    Thats for sure very strange. Have you tried opening a second session as root and killing the tasks likewise from there?
    Please tell me: How long has your system been running without rest?

    TheMask.
    CHECK OUT THESE GitHub PROJECTS!

    https://secupwn.github.io/Android-IMSI-Catcher-Detector/
    https://github.com/SecUpwN/Spotify-AdKiller

  5. #5
    Join Date
    Jun 2008
    Posts
    42

    Default Re: Kill unkillable task?

    kill -9 pid_of_process

  6. #6
    Join Date
    Oct 2008
    Location
    Birmingham. AL
    Posts
    858

    Default Re: Kill unkillable task?

    Or, pgrep process-name, that'll give you the ID, then kill with that.

    If processes are refusing to die, they're probably already hung. Entering "shutdown -r restart" as root at the CLI to force a reboot should be reasonably safe, too.

  7. #7
    Join Date
    Aug 2008
    Location
    127.0.0.1
    Posts
    22

    Default Re: Kill unkillable task?

    Axeia wrote:
    > On my server openSUSE 11.1 x86_64 KDE4.1 I got kacpi_notify taking up
    > 50% of the cpu and zypper taking up 300MB of RAM which seems to be
    > steadily growing..
    >
    > How do I kill these 2 as system monitor > Kill process doesn't do much
    > besides asking for a root password.
    >


    last time i check, kacpi_notify was part of kernel process. i think you
    should not kill it. just try to stop/kill zypper and see if kacpi_notify
    still taking up the cpu.

    > I'm reluctant to reboot as this will no doubt result in a disk error +
    > 6 hour recovery process, for which I quite frankly don't have the time.
    > Don't like the console view much either as the resolution isn't
    > supported on the monitor on the server, but I can drag my normal one to
    > it.
    >


    btw, how do you assume that reboot will result in disk error ? maybe it
    was just fsck process.

  8. #8
    Join Date
    Jul 2008
    Location
    Netherlands
    Posts
    1,140

    Default Re: Kill unkillable task?

    Quote Originally Posted by rv77ax View Post
    Axeia wrote:[color=blue]btw, how do you assume that reboot will result in disk error ? maybe it
    was just fsck process.
    It did that the last 8 out 10 reboots the 2 where it didn't it wasn't running for longer then a few minutes at most.

    Oh well got the rpm process killed, acpi is still at 50-65% cpu load, but I can live with that for now.
    Special effects <- KDE 4.2 Showing off
    More KDE -> PINK KDE

  9. #9
    Join Date
    Oct 2008
    Location
    Birmingham. AL
    Posts
    858

    Default Re: Kill unkillable task?

    I was bored so a did some googling.

    https://bugs.launchpad.net/ubuntu/+s...cpi/+bug/75174

    That's from the Ubuntu forum and the unit in question is a laptop, but that sounds suspiciously like your kacpi-notify problem. Just like you, even a kill -9 won't make it die, and then the computer hangs, requiring a hardware reboot.

    They recommend that you disable acpid (the acpi daemon) before shutting down.

    Interesting.

    Still don't know about your other problem.

Posting Permissions

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