From owner-freebsd-hackers@freebsd.org Thu Nov 28 19:24:46 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0A6321B492E for ; Thu, 28 Nov 2019 19:24:46 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 47P6z133bgz3yZG for ; Thu, 28 Nov 2019 19:24:45 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id BEB01A97BE; Thu, 28 Nov 2019 20:24:43 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRAfXtXtKt3c; Thu, 28 Nov 2019 20:24:43 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id EEA98A97BD; Thu, 28 Nov 2019 20:24:42 +0100 (CET) Subject: Re: Process in T state does not want to die..... To: Konstantin Belousov Cc: FreeBSD Hackers , Eugene Grosbein References: <966f830c-bf09-3683-90da-e70aa343cc16@digiware.nl> <3c57e51d-fa36-39a3-9691-49698e8d2124@grosbein.net> <91490c30-45e9-3c38-c55b-12534fd09e28@digiware.nl> <20191128115122.GN10580@kib.kiev.ua> From: Willem Jan Withagen Message-ID: <296874db-40f0-c7c9-a573-410e4c86049a@digiware.nl> Date: Thu, 28 Nov 2019 20:24:43 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <20191128115122.GN10580@kib.kiev.ua> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl X-Rspamd-Queue-Id: 47P6z133bgz3yZG X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wjw@digiware.nl designates 176.74.240.9 as permitted sender) smtp.mailfrom=wjw@digiware.nl X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[digiware.nl]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCVD_IN_DNSWL_MED(-0.20)[9.240.74.176.list.dnswl.org : 127.0.9.2]; IP_SCORE(-3.09)[ip: (-9.79), ipnet: 176.74.224.0/19(-4.89), asn: 28878(-0.81), country: NL(0.02)]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:28878, ipnet:176.74.224.0/19, country:NL]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Nov 2019 19:24:46 -0000 On 28-11-2019 12:51, Konstantin Belousov wrote: > 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 > Also useful is the output from > $ ps -o pid,lwp,flags,flags2,state,tracer,command -p > After that is shown, it could be determined where to look next. > What is your system version ? > This is 12.1 RELEASE... But I get this: # procstat -L 3448 procstat: sysctl method is not supported And # procstat -kk -L Gives me the help info --WjW