herd can't connect to socket on GNU/Hurd: Connection refused

herd can't connect to socket on GNU/Hurd: Connection refused

[Akib Azmain Turja]

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

I've downloaded latest QEMU image from build servers (build details:
https://ci.guix.gnu.org/build/618573/details).  Then I booted it with
libvirtd on my Guix System on GNU/Linux.  It booted and the login shell
appeared.  I logined as root without password and tried to install GNU
Hello (just to make sure everything is working).  It failed due to
network problems, although my host machine was connected to the
internet.  Then I tried to ping GNU server:

root@guixygnu ~# ping gnu.org

But no output appeared, not even an error message!  I checked the return
status immediately:

root@guixygnu ~# echo $?
1

Then I tried ping localhost, but again it returned 1 without any output.
Then tried to see the available interfaces, but this too failed:

root@guixygnu ~# ifconfig
ifconfig: could not get list of interfaces

Then I booted again with QEMU directly with:

$ qemu-system-i386 -m 512 -snapshot -hda <path/to/image.qcow2>

Again, I face the same problem.  However, this time I noticed a message
from settrans saying "settrans: /servers/socket/1: Device or resource
busy", a message saying the disk is mounted as read-only, (probably) an
error message from fsck showing it's usage, some warnings from Guile
saying "WARNING: (guile-user): imported module (guix build utils)
overrides core binding `delete'", the following messages during boot:

failed to start service: loopback
failed to start service: networking
failed to start service: ssh-daemon
failed to start service: ssh
failed to start service: sshd

Followed by an incomplete backtrace:

Backtrace:
           3 (primitive-load "/gnu/store/n9glgyqlb30wjxia0zcx71x9zw9?")
In shepherd.scm:

I saw many other messages, but I didn't get the time to read and copy
it.

Then I tried to check the status of loopback service:

root@guixygnu ~# herd status loopback
error: connect: /var/run/shepherd/socket: Connection refused

Can someone help me with this issue?  The QEMU image is almost unusable
without networking.

Note: all commands and their outputs are copied by hand.

--
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

Get it with:

    gpg --recv-keys 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5

See https://emailselfdefense.fsf.org/ to learn more and protect your
emails and yourself from surveillance.  Please send me encrypted
messages whenever possible.

Never send me Microsoft Office attachments, they use secret proprietary
format so I'll fail to read and trash them; send them in plain text if
possible or in formats like ODF and PDF if your document contains images
or videos. See http://www.gnu.org/philosophy/no-word-attachments.html to
learn more.

Please don't send HTML emails, use plain text.  HTML emails are usually
vulnerable, about thousand times larger than plain text and look ugly to
me.  They contain trackers, so whenever someone opens a messsage he is
tracked by third-party.  See http://www.asciiribbon.org to learn more.

()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

bug#50477: herd can't connect to socket on GNU/Hurd: Connection refused

[Ricardo Wurmus]

Hi,

ping not working inside qemu is a frequently encountered problem.  See
also the Hurd wiki:

  […] note that ping doesn't work with QEMU's user-networking stack.

https://www.gnu.org/software/hurd/hurd/running/qemu.html

> root@guixygnu ~# herd status loopback
> error: connect: /var/run/shepherd/socket: Connection refused

This means that shepherd isn’t running.  Can you reliably reproduce
this?

As it is this bug report does not contain enough information to be
actionable as we cannot easily reproduce the problem.  Could you please
provide more information?  Otherwise I’d like to close it.

Thank you!

-- 
Ricardo

bug#50477: herd can't connect to socket on GNU/Hurd: Connection refused

[Akib Azmain Turja via Bug reports for GNU Guix]

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

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi,
>
> ping not working inside qemu is a frequently encountered problem.  See
> also the Hurd wiki:
>
>   […] note that ping doesn't work with QEMU's user-networking stack.
>
> https://www.gnu.org/software/hurd/hurd/running/qemu.html

Yes, it says so.  But it's wrong, or the Debian's Hurd port was lying to
me.  On Debian, AFAIK ping works, I can't verify it right now, since my
Debian GNU/Hurd image is corrupt.  :(

>
>> root@guixygnu ~# herd status loopback
>> error: connect: /var/run/shepherd/socket: Connection refused
>
> This means that shepherd isn’t running.  Can you reliably reproduce
> this?

Yes.

>
> As it is this bug report does not contain enough information to be
> actionable as we cannot easily reproduce the problem.  Could you please
> provide more information?  Otherwise I’d like to close it.

Yes, it obviously lacks many information, because I didn't have them
then.  But now I have that information:

1.  Get a fresh build of the disk image.  I'm using
    8gk0vdbvz50xc2irps4ijbjpsb2im6qk-hurd-barebones.qcow2, downloaded on
    17th January 2022 (this year).

2.  Boot with the following:

--8<---------------cut here---------------start------------->8---
qemu-system-i386 -m 1G -hda <IMAGE> -device rtl8139,netdev=net0 \
  -netdev user,id=net0,hostfwd=tcp:127.0.0.1:10022-:2222
--8<---------------cut here---------------end--------------->8---

3.  Login as root.

4.  Test shepherd, it works.  Everything works.

5.  Reboot with "reboot" command.

6.  Login as root again.

7.  Test shepherd again, it no longer works, and it won't work ever.

>
> Thank you!
>
> -- 
> Ricardo
>
>
>

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]