From: "Ludovic Courtès" <ludo@gnu.org>
To: Nathan Dehnel <ncdehnel@gmail.com>
Cc: Guillaume Le Vaillant <glv@posteo.net>,
Mathieu Othacehe <othacehe@gnu.org>,
53225@debbugs.gnu.org
Subject: bug#53225: shepherd freezes if wireguard is started with dns config enabled
Date: Mon, 13 Jun 2022 11:31:18 +0200 [thread overview]
Message-ID: <87k09kucyh.fsf@gnu.org> (raw)
In-Reply-To: <CAEEhgEu2nOL6bEGYxrMdNjU8_Hoex-Xm1DMf4Kxj9M4ZEZ0uRg@mail.gmail.com> (Nathan Dehnel's message of "Sat, 11 Jun 2022 11:45:37 -0500")
Hi,
The /var/log/messages excerpt you sent me has nothing beyond:
> Jun 11 11:43:33 localhost shepherd[1]: Service networking has been started.
[…]
> Jun 11 11:43:33 localhost vmunix: [ 5.552395] wireguard: WireGuard
> 1.0.0 loaded. See www.wireguard.com for information.
> Jun 11 11:43:33 localhost vmunix: [ 5.552398] wireguard: Copyright
> (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights
> Reserved.
> Jun 11 11:43:33 localhost shepherd[1]: Failed to start wireguard-test
> in the background.
That there’s not a single error message from wireguard doesn’t help.
Mathieu, Guillaume: any idea what might prevent the wireguard Shepherd
service from starting, or how we could gather debugging info?
(Context: <https://issues.guix.gnu.org/53225>.)
Ludo’.
prev parent reply other threads:[~2022-06-13 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 0:27 bug#53225: shepherd freezes if wireguard is started with dns config enabled Nathan Dehnel
2022-01-13 15:11 ` Ludovic Courtès
2022-01-13 22:41 ` Nathan Dehnel
2022-01-17 13:48 ` Ludovic Courtès
2022-06-01 22:56 ` Nathan Dehnel
2022-06-02 13:38 ` Ludovic Courtès
2022-06-08 23:23 ` Nathan Dehnel
2022-06-09 15:05 ` Ludovic Courtès
2022-06-09 15:49 ` Nathan Dehnel
2022-06-09 20:15 ` Ludovic Courtès
[not found] ` <CAEEhgEu2nOL6bEGYxrMdNjU8_Hoex-Xm1DMf4Kxj9M4ZEZ0uRg@mail.gmail.com>
2022-06-13 9:31 ` Ludovic Courtès [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=87k09kucyh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=53225@debbugs.gnu.org \
--cc=glv@posteo.net \
--cc=ncdehnel@gmail.com \
--cc=othacehe@gnu.org \
/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).