From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#26931: GuixSD rebooting fails when tmux is running Date: Wed, 17 May 2017 09:39:45 +0200 Message-ID: <87inl00w5a.fsf@gnu.org> References: <20170514193043.GA5396@jasmine> <87lgpzqfxq.fsf@gnu.org> <20170516231839.GA22678@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dAtZy-0001Sf-F8 for bug-guix@gnu.org; Wed, 17 May 2017 03:41:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dAtZu-0001Vy-HC for bug-guix@gnu.org; Wed, 17 May 2017 03:41:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:46824) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dAtZu-0001Vu-Dx for bug-guix@gnu.org; Wed, 17 May 2017 03:41:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dAtZu-0000AM-8J for bug-guix@gnu.org; Wed, 17 May 2017 03:41:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20170516231839.GA22678@jasmine> (Leo Famulari's message of "Tue, 16 May 2017 19:18:39 -0400") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Leo Famulari Cc: 26931@debbugs.gnu.org Leo Famulari skribis: > On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Court=C3=A8s wrote: >> What does /var/log/shepherd.log show around the time where you hit >> =E2=80=9Chalt=E2=80=9D? >>=20 >> I get something like this: >>=20 >> --8<---------------cut here---------------start------------->8--- >> 18:06:26 Service mcron has been stopped. >> 18:06:26 sending all processes the TERM signal > > For me, this is where it gets stuck: > > ------ > 2017-05-16 19:12:53 sending all processes the TERM signal > 2017-05-16 19:12:58 waiting for process termination (processes left: (1 4= 94))=20 > 2017-05-16 19:13:00 waiting for process termination (processes left: (1 4= 94))=20 > 2017-05-16 19:13:02 waiting for process termination (processes left: (1 4= 94))=20 > ------ > > In my experience, it will wait here forever. > > And from `ps aux`: > > leo 494 0.0 0.1 27232 3676 ? Ss 19:12 0:00 tmux Interesting. The code for this is in (gnu services base). It sends SIGTERM, waits for a few seconds, and then sends SIGKILL, which processes cannot survive AFAIK, and then enters that =E2=80=98wait=E2=80=99= loop. This is on the bare metal and /etc/shepherd/do-not-kill does not exist, right? We could always add a round of SIGKILL in the =E2=80=98wait=E2=80=99 loop, = but that doesn=E2=80=99t sound right. Does /var/log/messages contain any hints as t= o why tmux wasn=E2=80=99t terminated? Thanks, Ludo=E2=80=99.