GNU bug report logs - #66297
guix-daemon not starting after boot

Previous Next

To reply to this bug, email your comments to 66297 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: guix-daemon not starting after boot
Date: Sun, 1 Oct 2023 22:45:26 +0100

Hi Guix!

After the recent pull and system reconfigure I've started experiencing
guix-daemon not starting up after the system boot.

~# guix describe
Generation 29   Sep 27 2023 21:59:12    (current)
  guix 0500af5
    repository URL: https://git.savannah.gnu.org/git/guix.git
    branch: master
    commit: 0500af5556307d0a4c14a23864e9e4bccd2643d7
  nonguix bb184bd
    repository URL: https://gitlab.com/nonguix/nonguix
    branch: master
    commit: bb184bd0a8f91beec3a00718759e96c7828853de

~# guix pull
guix pull: error: failed to connect to
`/var/guix/daemon-socket/socket': Connection refused
~# herd status guix-daemon
Status of guix-daemon:
  It is stopped.
  It is enabled.
  Provides (guix-daemon).
  Requires (user-processes).
  Will be respawned.

Logs are empty:
~# tail /var/log/guix-daemon.log | wc -l
0


-- 
… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.

Message #8 received at 66297 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 66297 <at> debbugs.gnu.org
Subject: Re: bug#66297: guix-daemon not starting after boot
Date: Thu, 05 Oct 2023 15:39:11 +0200

Hi,

Sharlatan Hellseher <sharlatanus <at> gmail.com> skribis:

> After the recent pull and system reconfigure I've started experiencing
> guix-daemon not starting up after the system boot.

Anything in /var/log/messages?

What does ‘herd log’ say?

Thanks,
Ludo’.

Message #11 received at 66297 <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 66297 <at> debbugs.gnu.org
Subject: Re: bug#66297: guix-daemon not starting after boot
Date: Tue, 10 Oct 2023 00:53:21 +0100

Hi,

I think I just get used to kick it manually and forgot to replay on
this issue =)

No Herd/Shepherd logs since Sept 30 in messages

 sudo grep -i "shepherd\|herd" /var/log/messages  | tail
grep: /var/log/messages: binary file matches
Sep 30 21:16:03 localhost shepherd[1]: Service console-font-tty3
running with value #t.
Sep 30 21:16:03 localhost shepherd[1]: Service console-font-tty4 started.
Sep 30 21:16:03 localhost vmunix: [    2.427621] shepherd[1]:
Sep 30 21:16:03 localhost vmunix: [    2.428262] shepherd[1]:
Sep 30 21:16:03 localhost vmunix: [    2.429207] shepherd[1]: Service
sysctl has been started.
Sep 30 21:16:03 localhost vmunix: [    2.429434] shepherd[1]: Service
sysctl started.
Sep 30 21:16:03 localhost vmunix: [    2.429666] shepherd[1]: Service
sysctl running with value #t.
Sep 30 21:16:03 localhost vmunix: [    2.430082] shepherd[1]: Starting
service virtual-terminal...
Sep 30 21:16:03 localhost vmunix: [    2.430416] shepherd[1]: Service
virtual-terminal started.
Sep 30 21:16:03 localhost vmunix: [    2.430649] shepherd[1]: Service
virtual-terminal running with value #t.

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

Thanks,
Oleg

On Thu, 5 Oct 2023 at 14:39, Ludovic Courtès <ludo <at> gnu.org> wrote:
>
> Hi,
>
> Sharlatan Hellseher <sharlatanus <at> gmail.com> skribis:
>
> > After the recent pull and system reconfigure I've started experiencing
> > guix-daemon not starting up after the system boot.
>
> Anything in /var/log/messages?
>
> What does ‘herd log’ say?
>
> Thanks,
> Ludo’.



-- 

… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.

Message #14 received at 66297 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 66297 <at> debbugs.gnu.org
Subject: Re: bug#66297: guix-daemon not starting after boot
Date: Thu, 12 Oct 2023 09:20:46 +0200

Hi Sharlatan,

Sharlatan Hellseher <sharlatanus <at> 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’.

Message #17 received at 66297 <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 66297 <at> debbugs.gnu.org
Subject: Re: bug#66297: guix-daemon not starting after boot
Date: Fri, 13 Oct 2023 01:32:55 +0100

[Message part 1 (text/plain, inline)]

Hi Ludo,

Thank you for your time and help.

I creaed a simple script, it may be helpfull for quick glance on guix healh in
general =)

I try to include all discussed steps I've tried to have a broad picture.

> ./guix-health.sh
> [1697156132.285]: [ PASS ] verification of required commands completed
> [1697156132.315]: [ PASS ] Guix socket file is present in /var/guix/daemon-socket/socket
> [1697156132.318]: [ WARN ] guix-daemon is stopped
> [1697156132.323]: [ WARN ] guix-daemon is not listed in current system config

Sharlatan Hellseher (1):
  etc: Add guix-health.sh

 etc/guix-health.sh | 145 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 145 insertions(+)
 create mode 100755 etc/guix-health.sh


base-commit: 5a3fb306535c2ec0a118f2f0bc8f6a162b85c7d6
-- 
2.41.0

On Thu, 12 Oct 2023 at 08:20, Ludovic Courtès <ludo <at> gnu.org> wrote:
>
> Hi Sharlatan,
>
> Sharlatan Hellseher <sharlatanus <at> 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’.



-- 

… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.

[0001-etc-Add-guix-health.sh.patch (text/x-patch, attachment)]

[guix-config.png (image/png, attachment)]

Message #20 received at 66297 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 66297 <at> debbugs.gnu.org
Subject: Re: bug#66297: guix-daemon not starting after boot
Date: Sat, 14 Oct 2023 19:46:23 +0200

Hello,

Sharlatan Hellseher <sharlatanus <at> gmail.com> skribis:

> I creaed a simple script, it may be helpfull for quick glance on guix healh in
> general =)

Heh.  :-)  Could you answer my earlier questions:

>> > 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?

TIA,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.