Date: Thu, 28 Nov 2019 13:51:22 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Willem Jan Withagen <wjw@digiware.nl> Cc: Eugene Grosbein <eugen@grosbein.net>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Process in T state does not want to die..... Message-ID: <20191128115122.GN10580@kib.kiev.ua> In-Reply-To: <91490c30-45e9-3c38-c55b-12534fd09e28@digiware.nl> References: <966f830c-bf09-3683-90da-e70aa343cc16@digiware.nl> <3c57e51d-fa36-39a3-9691-49698e8d2124@grosbein.net> <91490c30-45e9-3c38-c55b-12534fd09e28@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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 ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191128115122.GN10580>