GNU bug report logs - #47724
error: connect: /run/user/1000/shepherd/socket: No such file or directory

Previous Next

Full log

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Leo Famulari <leo <at> famulari.name>
Cc: bo0od <bo0od <at> riseup.net>, 47724 <at> debbugs.gnu.org
Subject: Re: bug#47724: error: connect: /run/user/1000/shepherd/socket: No
 such file or directory
Date: Sun, 18 Apr 2021 12:32:51 +0200

Hi,

Leo Famulari <leo <at> famulari.name> skribis:

> On Mon, Apr 12, 2021 at 12:54:14PM +0000, bo0od wrote:

[...]

>> To complete the upgrade, run 'herd restart SERVICE' to stop,
>> upgrade, and restart each service that was not automatically restarted.
>> Run 'herd status' to view the list of services on your system.
>> user <at> host ~$ herd restart term-auto
>> error: connect: /run/user/1000/shepherd/socket: No such file or directory
>> user <at> host ~$ herd status
>> error: connect: /run/user/1000/shepherd/socket: No such file or directory 
>
> The problem is that you need to be root to run these commands. We should
> adjust the hint to say that.

Note that ‘herd’ cannot guess whether you intend to talk to your user
shepherd and it’s not running, or whether you intend to talk to the
system shepherd.

So the hint should suggest both possibilities.

(At some point we should extract the diagnostic code of Guix and make it
a separate library so that the Shepherd can use it as well.)

Ludo’.

Previous Next

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