From: "Ludovic Courtès" <ludo@gnu.org>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 66297@debbugs.gnu.org
Subject: bug#66297: guix-daemon not starting after boot
Date: Thu, 12 Oct 2023 09:20:46 +0200 [thread overview]
Message-ID: <877cnspar5.fsf@gnu.org> (raw)
In-Reply-To: <CAO+9K5pYucxRUz4vOiBdgnd5HvUbpk+byWS+FJNmgx+t8hqu6A@mail.gmail.com> (Sharlatan Hellseher's message of "Tue, 10 Oct 2023 00:53:21 +0100")
Hi Sharlatan,
Sharlatan Hellseher <sharlatanus@gmail.com> skribis:
> I think I just get used to kick it manually and forgot to replay on
> this issue =)
Ouch. :-)
> sudo grep -i "shepherd\|herd" /var/log/messages | tail
> grep: /var/log/messages: binary file matches
Looks like grep didn’t actually output matches, did it?
Could you screen the file, starting from the latest boot, in search of
references to guix-daemon?
> There this no track of guix-daemon was starting in herd log
>
> herd log | grep daemon
> 10 Oct 2023 00:03:30 service upower-daemon is being started
> 10 Oct 2023 00:03:30 service upower-daemon is running
> 10 Oct 2023 00:03:30 service ssh-daemon is being started
> 10 Oct 2023 00:03:30 service ssh-daemon is running
What about ‘sudo herd status’? Does guix-daemon show up there?
Also, could you check:
guix system shepherd-graph /run/current-system/configuration.scm | \
guix shell xdot -- xdot -
to make sure guix-daemon actually is in your config, to be 100% sure?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-10-12 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 21:45 bug#66297: guix-daemon not starting after boot Sharlatan Hellseher
2023-10-05 13:39 ` Ludovic Courtès
2023-10-09 23:53 ` Sharlatan Hellseher
2023-10-12 7:20 ` Ludovic Courtès [this message]
2023-10-13 0:32 ` Sharlatan Hellseher
2023-10-14 17:46 ` Ludovic Courtès
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=877cnspar5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=66297@debbugs.gnu.org \
--cc=sharlatanus@gmail.com \
/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).