From: Leo Famulari <leo@famulari.name>
To: bo0od <bo0od@riseup.net>
Cc: 47724@debbugs.gnu.org
Subject: bug#47724: error: connect: /run/user/1000/shepherd/socket: No such file or directory
Date: Mon, 12 Apr 2021 14:24:13 -0400 [thread overview]
Message-ID: <YHSQTQbOfqc97Xnt@jasmine.lan> (raw)
In-Reply-To: <3e26aa4a-7e61-3e09-b554-b3c0910309c8@riseup.net>
On Mon, Apr 12, 2021 at 12:54:14PM +0000, bo0od wrote:
> Following manual installation on what to do after first boot:
>
> https://guix.gnu.org/en/manual/en/html_node/After-System-Installation.html
>
> "sudo guix system reconfigure /etc/config.scm"
>
> but running this command will request (after it finish) to restart some
> services which cant be restarted leading to the error in the title.
Thanks for the report...
> 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.
next prev parent reply other threads:[~2021-04-12 18:25 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 [this message]
2021-04-13 10:54 ` bo0od
2021-04-18 10:32 ` Ludovic Courtès
[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=YHSQTQbOfqc97Xnt@jasmine.lan \
--to=leo@famulari.name \
--cc=47724@debbugs.gnu.org \
--cc=bo0od@riseup.net \
/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).