From: "Ludovic Courtès" <ludo@gnu.org>
To: 41123@debbugs.gnu.org
Subject: bug#41123: shepherd exits for no good reason
Date: Thu, 07 May 2020 12:32:57 +0200 [thread overview]
Message-ID: <87bln0doh2.fsf@inria.fr> (raw)
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’.
next reply other threads:[~2020-05-07 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 10:32 Ludovic Courtès [this message]
2020-05-07 16:55 ` bug#41123: shepherd exits for no good reason Mathieu Othacehe
2020-05-10 10:38 ` Ludovic Courtès
2020-07-26 20:28 ` Mathieu Othacehe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bln0doh2.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=41123@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).