Cannot kill my lsof processes even as root











up vote
0
down vote

favorite












My lsof is hung so bad that I can't even kill -9 it.



Initially, it was owned by another process, foo. I tried killing foo, hoping that lsof would also go way. But while I was able to kill -9 foo, now lsof appears to be owned by `upstart.



root@box 0 L1 ~

$ ps -ef | grep 'lsof|upstart' | grep 3575

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       3575  3331  0 Nov26 ?        00:00:01 /sbin/upstart --user

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Next, I try to get a list of PIDs of lsof processes.



root@box 130 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }'

1595

1603

1605

1614

4330

4353

4429

4435

4580


I try to kill them all (as root).



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }' | xargs -n1 kill -9


But, they are still "hanging in" there. (pun intended)



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Notes:




  1. All of the above lsof commands were invoked by background tasks inside of foo.


  2. The lsof bar was invoked manually on the shell, and even it hung! I can Ctrl-C out of it. But it continues to show in the ps -ef listing.



Questions:




  1. Why is lsof hanging in the first place? All the files given as arguments to lsof are on a local ext4 filesystem of a Ubuntu 16.04 box.


  2. Why even kill -9 isn't able to kill these processes - even when run as root?


  3. Why I can Ctrl-C an interactively invoked lsof bar just fine but the lsof bar continues to show up in the ps -ef listing?







root kill lsof hang







share|improve this question




















  • 2




    Your second and third questions may find answers here.
    – fra-san
    2 days ago















up vote
0
down vote

favorite












My lsof is hung so bad that I can't even kill -9 it.



Initially, it was owned by another process, foo. I tried killing foo, hoping that lsof would also go way. But while I was able to kill -9 foo, now lsof appears to be owned by `upstart.



root@box 0 L1 ~

$ ps -ef | grep 'lsof|upstart' | grep 3575

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       3575  3331  0 Nov26 ?        00:00:01 /sbin/upstart --user

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Next, I try to get a list of PIDs of lsof processes.



root@box 130 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }'

1595

1603

1605

1614

4330

4353

4429

4435

4580


I try to kill them all (as root).



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }' | xargs -n1 kill -9


But, they are still "hanging in" there. (pun intended)



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Notes:




  1. All of the above lsof commands were invoked by background tasks inside of foo.


  2. The lsof bar was invoked manually on the shell, and even it hung! I can Ctrl-C out of it. But it continues to show in the ps -ef listing.



Questions:




  1. Why is lsof hanging in the first place? All the files given as arguments to lsof are on a local ext4 filesystem of a Ubuntu 16.04 box.


  2. Why even kill -9 isn't able to kill these processes - even when run as root?


  3. Why I can Ctrl-C an interactively invoked lsof bar just fine but the lsof bar continues to show up in the ps -ef listing?







root kill lsof hang







share|improve this question




















  • 2




    Your second and third questions may find answers here.
    – fra-san
    2 days ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











My lsof is hung so bad that I can't even kill -9 it.



Initially, it was owned by another process, foo. I tried killing foo, hoping that lsof would also go way. But while I was able to kill -9 foo, now lsof appears to be owned by `upstart.



root@box 0 L1 ~

$ ps -ef | grep 'lsof|upstart' | grep 3575

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       3575  3331  0 Nov26 ?        00:00:01 /sbin/upstart --user

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Next, I try to get a list of PIDs of lsof processes.



root@box 130 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }'

1595

1603

1605

1614

4330

4353

4429

4435

4580


I try to kill them all (as root).



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }' | xargs -n1 kill -9


But, they are still "hanging in" there. (pun intended)



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Notes:




  1. All of the above lsof commands were invoked by background tasks inside of foo.


  2. The lsof bar was invoked manually on the shell, and even it hung! I can Ctrl-C out of it. But it continues to show in the ps -ef listing.



Questions:




  1. Why is lsof hanging in the first place? All the files given as arguments to lsof are on a local ext4 filesystem of a Ubuntu 16.04 box.


  2. Why even kill -9 isn't able to kill these processes - even when run as root?


  3. Why I can Ctrl-C an interactively invoked lsof bar just fine but the lsof bar continues to show up in the ps -ef listing?







root kill lsof hang







share|improve this question















My lsof is hung so bad that I can't even kill -9 it.



Initially, it was owned by another process, foo. I tried killing foo, hoping that lsof would also go way. But while I was able to kill -9 foo, now lsof appears to be owned by `upstart.



root@box 0 L1 ~

$ ps -ef | grep 'lsof|upstart' | grep 3575

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       3575  3331  0 Nov26 ?        00:00:01 /sbin/upstart --user

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Next, I try to get a list of PIDs of lsof processes.



root@box 130 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }'

1595

1603

1605

1614

4330

4353

4429

4435

4580


I try to kill them all (as root).



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep | gawk '{ print $2 }' | xargs -n1 kill -9


But, they are still "hanging in" there. (pun intended)



root@box 0 L1 ~

$ ps -ef | grep lsof | grep -v grep

joe       1595  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       1603  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.13

joe       1605  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       1614  3575  0 12:43 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.16

joe       4330  3575  0 12:53 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4353  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4429  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.18

joe       4435  3575  0 12:54 pts/5    00:00:00 lsof /home/joe/tmp/a a/file.11

joe       4580  3575  0 12:55 pts/5    00:00:00 lsof bar


Notes:




  1. All of the above lsof commands were invoked by background tasks inside of foo.


  2. The lsof bar was invoked manually on the shell, and even it hung! I can Ctrl-C out of it. But it continues to show in the ps -ef listing.



Questions:




  1. Why is lsof hanging in the first place? All the files given as arguments to lsof are on a local ext4 filesystem of a Ubuntu 16.04 box.


  2. Why even kill -9 isn't able to kill these processes - even when run as root?


  3. Why I can Ctrl-C an interactively invoked lsof bar just fine but the lsof bar continues to show up in the ps -ef listing?







root kill lsof hang




root kill lsof hang






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago

























asked 2 days ago









Harry

3701313




3701313








  • 2




    Your second and third questions may find answers here.
    – fra-san
    2 days ago














  • 2




    Your second and third questions may find answers here.
    – fra-san
    2 days ago








2




2




Your second and third questions may find answers here.
– fra-san
2 days ago




Your second and third questions may find answers here.
– fra-san
2 days ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486740%2fcannot-kill-my-lsof-processes-even-as-root%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f486740%2fcannot-kill-my-lsof-processes-even-as-root%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
Read more

Can't connect RFCOMM socket: Host is down

Image
up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
Read more

Kernel panic - not syncing: Fatal Exception in Interrupt

Image
0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
Read more