error: connect: /run/user/1000/shepherd/socket: No such file or directory

  • Done
  • quality assurance status badge
Details
3 participants
  • bo0od
  • Leo Famulari
  • Ludovic Courtès
Owner
unassigned
Submitted by
bo0od
Severity
normal

Debbugs page

B
(address . bug-guix@gnu.org)
3e26aa4a-7e61-3e09-b554-b3c0910309c8@riseup.net
Hi There,

Following manual installation on what to do after first boot:


"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.

check the uploaded .txt file.

ThX!
user@host ~$ sudo guix system reconfigure /etc/config.scm
The following derivation will be built:
/gnu/store/sqj0jnif08jvbzb48jpdjwggymcjzl2q-grub.cfg.drv

building /gnu/store/sqj0jnif08jvbzb48jpdjwggymcjzl2q-grub.cfg.drv...
/gnu/store/5c6v18yrx65pnzacs1biqy7pzlfi6rsf-system
/gnu/store/kmdr3c6y3hbf0zm4gxmnzlsf5j907r6c-grub.cfg

activating system...
making '/gnu/store/5c6v18yrx65pnzacs1biqy7pzlfi6rsf-system' the current system...
setting up setuid programs in '/run/setuid-programs'...
populating /etc from /gnu/store/rcf9bsdlc2dr297ydf3l86ibilsrfqky-etc...
The following derivation will be built:
/gnu/store/lam5sjwwznx8f3mssiwfsa7cvldyccxr-install-bootloader.scm.drv

building /gnu/store/lam5sjwwznx8f3mssiwfsa7cvldyccxr-install-bootloader.scm.drv...
guix system: bootloader successfully installed on '/dev/xvda'
shepherd: Service host-name has been started.
shepherd: Service user-homes has been started.
shepherd: Service sysctl has been started.
shepherd: Service host-name has been started.
shepherd: Service term-auto could not be started.
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
L
L
Leo Famulari wrote on 12 Apr 2021 11:24
(name . bo0od)(address . bo0od@riseup.net)(address . 47724@debbugs.gnu.org)
YHSQTQbOfqc97Xnt@jasmine.lan
On Mon, Apr 12, 2021 at 12:54:14PM +0000, bo0od wrote:
Toggle quote (9 lines)
> 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...

Toggle quote (8 lines)
> 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.
B
(name . Leo Famulari)(address . leo@famulari.name)(address . 47724@debbugs.gnu.org)
e82cec96-324c-45e3-4bb9-06ba2fa107b3@riseup.net
Toggle quote (1 lines)
> The problem is that you need to be root to run these commands. We should
> adjust the hint to say that.

Yes please, And make the error message sane/understandable with human
language as i couldnt understand from the error message oh it needs root
access because it doesnt say that anywhere.

Leo Famulari:
Toggle quote (23 lines)
> 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.
>
L
L
Ludovic Courtès wrote on 18 Apr 2021 03:32
(name . Leo Famulari)(address . leo@famulari.name)
87im4jlw6k.fsf@gnu.org
Hi,

Leo Famulari <leo@famulari.name> skribis:

Toggle quote (2 lines)
> On Mon, Apr 12, 2021 at 12:54:14PM +0000, bo0od wrote:

[...]

Toggle quote (11 lines)
>> 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’.
L
L
Ludovic Courtès wrote on 2 May 2021 15:02
control message for bug #47724
(address . control@debbugs.gnu.org)
87v980ztdp.fsf@gnu.org
tags 47724 notabug
close 47724
quit
B
B
bo0od wrote on 2 May 2021 17:31
Re: bug#47724 acknowledged by developer (control message for bug #47724)
(address . 47724@debbugs.gnu.org)
b7ff3c2f-d936-ed10-d9b0-a1199f7196d8@riseup.net
Its more of an enhancement not a bug. Did the popup message put in any
better way than the current state?

GNU bug Tracking System:
Toggle quote (13 lines)
> This is an automatic notification regarding your bug report
> #47724: error: connect: /run/user/1000/shepherd/socket: No such file or directory,
> which was filed against the guix package.
>
> Thank you for your report, which has now been closed.
> You can view the full report at
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=47724
>
> If you require further information, please followup to 47724@debbugs.gnu.org.
>
> debbugs.gnu.org maintainers
> (administrator, GNU bugs database)
>
?
Your comment

This issue is archived.

To comment on this conversation send an email to 47724@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 47724
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch