unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: bo0od <bo0od@riseup.net>, 47724@debbugs.gnu.org
Subject: bug#47724: error: connect: /run/user/1000/shepherd/socket: No such file or directory
Date: Sun, 18 Apr 2021 12:32:51 +0200	[thread overview]
Message-ID: <87im4jlw6k.fsf@gnu.org> (raw)
In-Reply-To: <YHSQTQbOfqc97Xnt@jasmine.lan> (Leo Famulari's message of "Mon, 12 Apr 2021 14:24:13 -0400")

Hi,

Leo Famulari <leo@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@host ~$ herd restart term-auto
>> error: connect: /run/user/1000/shepherd/socket: No such file or directory
>> user@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’.




  parent reply	other threads:[~2021-04-18 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v980ztdp.fsf@gnu.org>
2021-04-12 12:54 ` bug#47724: error: connect: /run/user/1000/shepherd/socket: No such file or directory bo0od
2021-04-12 18:24   ` Leo Famulari
2021-04-13 10:54     ` bo0od
2021-04-18 10:32     ` Ludovic Courtès [this message]
     [not found]   ` <handler.47724.C.161999297113642.notifdonectrl.0@debbugs.gnu.org>
2021-05-03  0:31     ` bug#47724: acknowledged by developer (control message for bug #47724) bo0od

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=87im4jlw6k.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=47724@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    --cc=leo@famulari.name \
    /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).