Timeline for unkillable/unstoppable normal user process, how to forcedly control it?
Current License: CC BY-SA 3.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 20, 2017 at 18:55 | history | edited | Jeff Schaller♦ | CC BY-SA 3.0 |
English contractions use apostrophes.
|
| Aug 19, 2017 at 21:19 | history | tweeted | twitter.com/StackUnix/status/899017927319539714 | ||
| Aug 19, 2017 at 18:37 | history | edited | Aquarius Power | CC BY-SA 3.0 |
edited title
|
| Aug 17, 2017 at 23:25 | comment | added | Gilles 'SO- stop being evil' | Is this an epidemic? If many people are having the same problem all of a sudden, maybe a recent kernel upgrade is buggy? (Unlikely though to have the same bug on RHEL and Ubuntu as they use different kernel versions.) | |
| Aug 17, 2017 at 21:39 | answer | added | Aquarius Power | timeline score: 3 | |
| Aug 17, 2017 at 21:13 | history | edited | Aquarius Power | CC BY-SA 3.0 |
added 169 characters in body
|
| Aug 17, 2017 at 21:06 | comment | added | Aquarius Power |
@HaukeLaging I stopped apparmor, tried STOP, KILL, ABRT signals on the find pid, but none worked. I tried to cat on many files at /proc/2315444 (at syscall it says running) even using sudo for that, but the most thing I get at dmesg is just like ptrace of pid 2315444 was attempted by: cat (pid 446803)
|
|
| Aug 17, 2017 at 20:47 | comment | added | Hauke Laging |
Then it should be very simple: Turn off AppArmor and see if the problem disappears. There need not be a configuration for find anyway: AppArmor permissions and restrictions are inherited.
|
|
| Aug 17, 2017 at 20:44 | history | edited | Aquarius Power | CC BY-SA 3.0 |
added 206 characters in body
|
| Aug 17, 2017 at 20:23 | history | edited | Aquarius Power | CC BY-SA 3.0 |
added 41 characters in body
|
| Aug 17, 2017 at 20:21 | comment | added | Aquarius Power |
@HaukeLaging apparmor is running but find is not listed on it. SELinux is not. found no way to determine if LSM is running yet. Tried to kill with SIGSTOP at the strace pid, but it didnt affect the find process, not sure if is that what you meant either, to kill the strace process just kills it only, nothing changes on dmesg either other than ptrace of pid 2315444 was attempted by: strace (pid 153868)
|
|
| Aug 17, 2017 at 20:08 | history | edited | Aquarius Power | CC BY-SA 3.0 |
added 113 characters in body
|
| Aug 17, 2017 at 20:03 | comment | added | Aquarius Power | @HaukeLaging if I have to active these (AppArmor, SELinux, LSM) on ubuntu 16.04, then I guess they are not cause I dont remember activating them in the past. But I guess I should make it sure in some way, will research about them. Kill thru strace (like I could use it as a kind of shell?) I will research about it. And indeed, the signal not reaching the process seems a great guess, will look more on it too thx! | |
| Aug 17, 2017 at 19:58 | comment | added | Hauke Laging |
That is very strange. I assume that the signal does not reach the process. Is AppArmor, SELinux or another LSM active? You may run kill through strace and have a look at the output of dmesg.
|
|
| Aug 17, 2017 at 19:58 | comment | added | Aquarius Power |
@Jesse_b no I cant use kill with it: bash: kill: (2309051) - No such process
|
|
| Aug 17, 2017 at 19:55 | comment | added | Aquarius Power | @Jesse_b it seems PGID is not accessible as a PID thru kill, so I guess we need some other command to deal with PGID(s), I got a bit lost on that answer btw, still trying to understand it :), I will try to keep my machine as long as possible running b4 rebooting, as I wont be able to try anything else after it; My guess is it can be a kernel bug? | |
| Aug 17, 2017 at 19:52 | comment | added | jesse_b |
You can kill a pgid with the kill command the same you would a pid. Not entirely sure about the rest though, but this may help? unix.stackexchange.com/questions/385105/…
|
|
| Aug 17, 2017 at 19:51 | comment | added | Aquarius Power | @Jesse_b stackoverflow.com/a/41498519/1422630, killing the PPID did not work, it is just reparented now; I am not sure if I can kill a PGID yet tho, or how to do it and if it will affect other applications? researching.. | |
| Aug 17, 2017 at 19:45 | comment | added | Aquarius Power | @thrig strace outputted nothing after saying it was attached, I had to sudo SIGKILL the strace process as ctrl+c could not stop it, after a long wait for output | |
| Aug 17, 2017 at 19:42 | comment | added | jesse_b |
This is a bit over my head but in my limited experience the PGID should be the same as the PID of the parent process. You should be able to modify your ps command to: ps -o pgid,pid,stat,status,state,pcpu,cmd
|
|
| Aug 17, 2017 at 19:41 | comment | added | Aquarius Power | interesting, I ended the top script but a sub script is still active as it's parent, so its parent is not pid 1; I will try kill the parent pid to see what happens; I dont know what is PGID yet, for test should I try it first? | |
| Aug 17, 2017 at 19:41 | comment | added | thrig |
Can you strace it to maybe see what it's doing?
|
|
| Aug 17, 2017 at 19:39 | history | edited | Aquarius Power | CC BY-SA 3.0 |
added 354 characters in body
|
| Aug 17, 2017 at 19:37 | comment | added | jesse_b | Is it running in it's own PGID or is it still under the PGID of your script? If the latter, have you tried to kill -9 the whole process group? | |
| Aug 17, 2017 at 19:33 | comment | added | Aquarius Power |
@Jesse_b thats -SIGKILL at kill -l :)
|
|
| Aug 17, 2017 at 19:31 | comment | added | jesse_b |
Have you tried kill -9?
|
|
| Aug 17, 2017 at 19:26 | history | asked | Aquarius Power | CC BY-SA 3.0 |