From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 63678@debbugs.gnu.org
Subject: bug#63678: Can't restart/halt system with shepherd 0.9.3 after upgrading
Date: Thu, 25 May 2023 14:20:48 +0100 [thread overview]
Message-ID: <87fs7k4kc1.fsf@cbaines.net> (raw)
In-Reply-To: <878rdceeq5.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Christopher Baines <mail@cbaines.net> skribis:
>
>> On a system running shepherd 0.9.3 [1], I've reconfigured, but now can't
>> reboot or halt.
>>
>> root@hamal ~# halt
>> Service root is not running.
>
> Hey, why halt it if it’s not running?
>
> Seriously though, any insight from /var/log/messages? I upgraded a
> bunch of machines and didn’t hit this particular problem. Bruno
> reported a similar problem with 0.9.3, but this had nothing to do with
> the upgrade:
>
> https://issues.guix.gnu.org/62619
>
> Could it be the same problem? Do you see:
>
> Assertion (eq? (canonical-name new) (canonical-name old)) failed.
>
> in /var/log/messages?
I don't see that, but I think these are the relevant log messages:
May 24 11:17:02 localhost shepherd[1]: Evaluating user expression (and (defined? (quote transient?)) (map (# ?) ?)).
May 24 11:17:02 localhost shepherd[1]: Evaluating user expression (register-services (primitive-load "/gnu/st?") ?).
May 24 11:17:03 localhost shepherd[1]: Service host-name has been started.
May 24 11:17:03 localhost shepherd[1]: Service user-homes has been started.
May 24 11:17:03 localhost shepherd[1]: [sysctl] fs.protected_hardlinks = 1
May 24 11:17:03 localhost shepherd[1]: [sysctl] fs.protected_symlinks = 1
May 24 11:18:41 localhost shepherd[1]: Exiting shepherd...
May 24 11:18:46 localhost shepherd[1]: Grace period of 5 seconds is over; sending -337 SIGKILL.
May 24 11:23:55 localhost shepherd[1]: Service root is not running.
May 24 11:24:16 localhost last message repeated 2 times
May 24 11:30:49 localhost syslogd (GNU inetutils 2.3): restart
May 24 11:30:49 localhost vmunix: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd083]
May 24 11:30:49 localhost vmunix: [ 0.000000] Linux version 6.3.3-arm64-generic (guix@guix) (gcc (GCC) 11.3.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT 1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-05-25 13:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:27 bug#63678: Can't restart/halt system with shepherd 0.9.3 after upgrading Christopher Baines
2023-05-25 13:13 ` Ludovic Courtès
2023-05-25 13:20 ` Christopher Baines [this message]
2023-05-27 17:04 ` Ludovic Courtès
2023-05-29 18:33 ` Christopher Baines
2023-06-06 15:06 ` Ludovic Courtès
2023-06-07 14:09 ` Christopher Baines
2024-03-20 18:09 ` Ludovic Courtès
2023-05-29 19:19 ` david larsson
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=87fs7k4kc1.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63678@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).