From one of my scripts, I called find
command, as a normal user (not root).
It was not returning/continuing, so I killed the script and find
is still running.
At htop
I see it is always using 100% of one core (4 cores here).
The core at 100% changes from time to time btw.
At htop, its state is 'R' (running), won't change after kill signals below.
I have tried: SIGKILL, SIGSTOP, SIGTERM, SIGABRT, hup, 15, none works.
Neither using sudo
.
I tried also all possible kill signals:
astr=(`kill -l |grep "..[)]" -o |tr -d ')'`)
for str in "${astr[@]}"; do echo "======== $str";kill -$str 2315444;ps -o pid,stat,status,state,pcpu,cmd -p 2315444;sleep 1;done
but after each, the result is always the same:
PID STAT STATUS S %CPU CMD
2315444 RN - R 99.5 find
apparmor
is running but find
is not listed on it (after checking), but stopping it didn't work either. SELinux is not running and I found yet no way to check for LSM here yet.
thinking about this I tried to forcefully umount the partition it was running at (what would cause no problem), and after doing so, find
was still running.
What else can I try, other than reboot?
There is nothing special at dmesg either.
Could it be a hardware failure? or a kernel bug?
I think it could have happened with any other process, not sure though. Maybe it is related to process that does hard drive IO?
OS.: Ubuntu 16.04
kill -9
? – jesse_b Aug 17 '17 at 19:31kill -l
:) – Aquarius Power Aug 17 '17 at 19:33strace
it to maybe see what it's doing? – thrig Aug 17 '17 at 19:41ps -o pgid,pid,stat,status,state,pcpu,cmd
– jesse_b Aug 17 '17 at 19:42kill
command the same you would a pid. Not entirely sure about the rest though, but this may help? https://unix.stackexchange.com/questions/385105/can-kill-in-bash-send-a-signal-only-to-a-single-process-whose-process-group-ha/385108#385108 – jesse_b Aug 17 '17 at 19:52bash: kill: (2309051) - No such process
– Aquarius Power Aug 17 '17 at 19:58kill
throughstrace
and have a look at the output ofdmesg
. – Hauke Laging Aug 17 '17 at 19:58find
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 thefind
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 thanptrace of pid 2315444 was attempted by: strace (pid 153868)
– Aquarius Power Aug 17 '17 at 20:21find
anyway: AppArmor permissions and restrictions are inherited. – Hauke Laging Aug 17 '17 at 20:47find
pid, but none worked. I tried tocat
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 likeptrace of pid 2315444 was attempted by: cat (pid 446803)
– Aquarius Power Aug 17 '17 at 21:06