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

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

[bo0od]

[-- Attachment #1: Type: text/plain, Size: 376 bytes --]

Hi There,

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.

check the uploaded .txt file.

ThX!

[-- Attachment #2: herderr.txt --]
[-- Type: text/plain, Size: 1463 bytes --]

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 

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

[Leo Famulari]

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.

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

[bo0od]

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

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

[Ludovic Courtès]

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

bug#47724: acknowledged by developer (control message for bug #47724)

[bo0od]

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:
> 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)
>