Process in T state does not want to die.....

[Eugene Grosbein]

28.11.2019 17:37, Willem Jan Withagen wrote:

>> Process in state T is STOPPED and prohibited for execution.
>> It cannot even process signal like SIGTERM or SIGKILL because they are queied waiting for continuation.
>> You need to resume it with kill -CONT first.
> 
> Tried that several times, but does not really have any effect.
> I could check and see if the signals (TERM, KILL) were waiting somewhere?
> With procstat??
> 
> But the original question was more for a way on preventing this state of affairs.
> Because uptill now the only resolution was to reboot the server, which is not a nice
> thing for a storage sollution.
> 
> Hence the: how to debug? question.

Sometimes background process is (mistakenly) started without closing/redirecting output
and if it tries to print something, it might get stopped depending on used shell.

Use ktrace/kdump to verify what's going on with the process if you can reproduce the problem.
You did not specify which version you use. Sometimes flags shown by ps are wrong due to kernel bugs
and corrupted process state flag and process is not really Stopped but Exiting for example.

ktrace/kdump should show if process got SIGSTOP/SIGTSTP really. And if SIGCONT was delivered.