unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 41123@debbugs.gnu.org
Subject: bug#41123: shepherd exits for no good reason
Date: Thu, 07 May 2020 18:55:10 +0200	[thread overview]
Message-ID: <87imh7elch.fsf@gmail.com> (raw)
In-Reply-To: <87bln0doh2.fsf@inria.fr> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22\?\= \=\?utf-8\?Q\?'s\?\= message of "Thu, 07 May 2020 12:32:57 +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




  reply	other threads:[~2020-05-07 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07 10:32 bug#41123: shepherd exits for no good reason Ludovic Courtès
2020-05-07 16:55 ` Mathieu Othacehe [this message]
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=87imh7elch.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=41123@debbugs.gnu.org \
    --cc=ludo@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).