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

[Konstantin Belousov]

On Thu, Nov 28, 2019 at 11:37:50AM +0100, Willem Jan Withagen wrote:
> On 27-11-2019 16:36, Eugene Grosbein wrote:
> > 27.11.2019 22:11, Willem Jan Withagen wrote:
> >
> > [skip]
> >
> > 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.

Start with the output from
	$ procstat -kk -L <pid>
Also useful is the output from
	$ ps -o pid,lwp,flags,flags2,state,tracer,command -p <pid>
After that is shown, it could be determined where to look next.
What is your system version ?