bug#41123: closed (shepherd exits for no good reason)

[GNU bug Tracking System]

Your message dated Sun, 26 Jul 2020 22:28:05 +0200
with message-id <875zaa81ii.fsf@gnu.org>
and subject line Re: bug#41123: shepherd exits for no good reason
has caused the debbugs.gnu.org bug report #41123,
regarding shepherd exits for no good reason
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
41123: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41123
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> shepherd exits for no good reason
>
>
>
>
> Date: 
>
> Thu, 07 May 2020 12:32:57 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
>
>
>
>
> 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’.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#41123: shepherd exits for no good reason
>
>
>
>
> Date: 
>
> Sun, 26 Jul 2020 22:28:05 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
>
>
>
>
> 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
>
>
> --- End Message ---