bug#41123: shepherd exits for no good reason
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
bug#41123: shepherd exits for no good reason
Hi, Mathieu Othacehe 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’.
bug#41123: shepherd exits for no good reason
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
bug#41123: shepherd exits for no good reason
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’.
