GNU bug report logs - #41123
shepherd exits for no good reason

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 41123 in the body.
You can then email your comments to 41123 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: shepherd exits for no good reason
Date: Thu, 07 May 2020 12:32:57 +0200

Hello,

I witnessed a case with Shepherd 0.8.0 on ‘core-updates’
(7b07852ddb334c92bcef69666f21c599f1f0fa79) where shepherd exited all by
itself, all of a sudden.  Here’s what /var/log/messages shows:

--8<---------------cut here---------------start------------->8---
May  7 09:36:23 localhost vmunix: [   20.316829] shepherd[1]: Service user-homes has been started.
May  7 09:36:23 localhost vmunix: [   21.319625] shepherd[1]: Service nscd has been started.
May  7 09:36:23 localhost vmunix: [   21.321029] shepherd[1]: Service guix-daemon has been started.

[…]

May  7 09:36:52 localhost shepherd[1]: Exiting shepherd... 
May  7 09:36:52 localhost shepherd[1]: Service xorg-server has been stopped. 
May  7 09:36:52 localhost shepherd[1]: Service console-font-tty2 has been stopped. 
May  7 09:36:52 localhost shepherd[1]: Service term-tty2 has been stopped. 
May  7 09:36:52 localhost shepherd[1]: Service upower-daemon has been stopped. 
May  7 09:36:52 localhost shepherd[1]: Service elogind has been stopped. 
May  7 09:36:52 localhost ntpd[482]: ntpd exiting on signal 15 (Terminated)
May  7 09:36:52 localhost syslogd: exiting on signal 15
--8<---------------cut here---------------end--------------->8---

The end result was a kernel panic with exitcode=0x100 (meaning exited
with 1).

It looks as though one had run ‘herd stop root’.

Ludo’.

Message #8 received at 41123 <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <m.othacehe <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 41123 <at> debbugs.gnu.org
Subject: Re: bug#41123: shepherd exits for no good reason
Date: Thu, 07 May 2020 18:55:10 +0200

Hey Ludo,

> May  7 09:36:52 localhost shepherd[1]: Exiting shepherd... 
> May  7 09:36:52 localhost shepherd[1]: Service xorg-server has been stopped. 
> May  7 09:36:52 localhost shepherd[1]: Service console-font-tty2 has been stopped. 
> May  7 09:36:52 localhost shepherd[1]: Service term-tty2 has been stopped. 
> May  7 09:36:52 localhost shepherd[1]: Service upower-daemon has been stopped. 
> May  7 09:36:52 localhost shepherd[1]: Service elogind has been stopped. 
> May  7 09:36:52 localhost ntpd[482]: ntpd exiting on signal 15 (Terminated)
> May  7 09:36:52 localhost syslogd: exiting on signal 15
>
> The end result was a kernel panic with exitcode=0x100 (meaning exited
> with 1).
>
> It looks as though one had run ‘herd stop root’.

It could be related to this bug[1]. The problem is that on 0.8.0 a
process restart can cause a root-service stop.

On your log, I can't see a process being restarted, so it might also be
unrelated.

Mathieu

[1]: https://lists.gnu.org/archive/html/bug-guix/2020-05/msg00085.html

Message #11 received at 41123 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Mathieu Othacehe <m.othacehe <at> gmail.com>
Cc: 41123 <at> debbugs.gnu.org
Subject: Re: bug#41123: shepherd exits for no good reason
Date: Sun, 10 May 2020 12:38:18 +0200

Hi,

Mathieu Othacehe <m.othacehe <at> gmail.com> skribis:

>> May  7 09:36:52 localhost shepherd[1]: Exiting shepherd... 
>> May  7 09:36:52 localhost shepherd[1]: Service xorg-server has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service console-font-tty2 has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service term-tty2 has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service upower-daemon has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service elogind has been stopped. 
>> May  7 09:36:52 localhost ntpd[482]: ntpd exiting on signal 15 (Terminated)
>> May  7 09:36:52 localhost syslogd: exiting on signal 15
>>
>> The end result was a kernel panic with exitcode=0x100 (meaning exited
>> with 1).
>>
>> It looks as though one had run ‘herd stop root’.
>
> It could be related to this bug[1]. The problem is that on 0.8.0 a
> process restart can cause a root-service stop.
>
> On your log, I can't see a process being restarted, so it might also be
> unrelated.

It looks very much the same though: it’s stopping itself, which most
likely happens as a result of killing itself.  I’ve merged them, we’ll
see!

Ludo’.

Message #18 received at 41123-done <at> debbugs.gnu.org (full text, mbox):

From: Mathieu Othacehe <othacehe <at> gnu.org>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 41123-done <at> debbugs.gnu.org
Subject: Re: bug#41123: shepherd exits for no good reason
Date: Sun, 26 Jul 2020 22:28:05 +0200

Hey,

> It looks very much the same though: it’s stopping itself, which most
> likely happens as a result of killing itself.  I’ve merged them, we’ll
> see!

This is probably fixed in Shepherd 0.8.1. Closing this one.

Thanks,

Mathieu

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.