From: Akib Azmain Turja via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>, 50477@debbugs.gnu.org
Subject: bug#50477: herd can't connect to socket on GNU/Hurd: Connection refused
Date: Wed, 13 Jul 2022 19:34:37 +0600 [thread overview]
Message-ID: <87edypyw42.fsf@disroot.org> (raw)
In-Reply-To: <87h73mxir6.fsf@elephly.net>
[-- 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 --]
prev parent reply other threads:[~2022-07-13 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 8:48 herd can't connect to socket on GNU/Hurd: Connection refused Akib Azmain Turja
2022-07-12 18:53 ` bug#50477: " Ricardo Wurmus
2022-07-13 13:34 ` Akib Azmain Turja via Bug reports for GNU Guix [this message]
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=87edypyw42.fsf@disroot.org \
--to=bug-guix@gnu.org \
--cc=50477@debbugs.gnu.org \
--cc=akib@disroot.org \
--cc=rekado@elephly.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).