From: Nathan Dehnel <ncdehnel@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 53225@debbugs.gnu.org
Subject: bug#53225: shepherd freezes if wireguard is started with dns config enabled
Date: Thu, 9 Jun 2022 10:49:07 -0500 [thread overview]
Message-ID: <CAEEhgEtUOiw4UyZn3_40LPrGBOTPsK36E75YL=6Fw7gsW15VzQ@mail.gmail.com> (raw)
In-Reply-To: <87tu8t3mjj.fsf@gnu.org>
>There should be lines like:
> shepherd[1]: Service 'wireguard-XXX' has been started.
>Perhaps they’ve been moved to a different files due to log rotation?
>Without these, I cannot tell what happened.
I tried it again and found this
Jun 9 10:47:44 localhost vmunix: [ 6.497581] wireguard: WireGuard
1.0.0 loaded. See www.wireguard.com for information.
Jun 9 10:47:44 localhost vmunix: [ 6.497584] wireguard: Copyright
(C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights
Reserved.
Jun 9 10:47:44 localhost shepherd[1]: Failed to start wireguard-test
in the background.
On Thu, Jun 9, 2022 at 10:05 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi Nathan,
>
> Nathan Dehnel <ncdehnel@gmail.com> skribis:
>
> >>Could you be more specific? Specifically, could you share
> >>/var/log/messages for the parts related to Wireguard?
> >
> > root@guixtest ~# cat /var/log/messages | grep -i wireguardJun 8
> > 18:20:07 localhost vmunix: [ 6.330271] wireguard: WireGuard 1.0.0
> > loaded. See www.wireguard.com for information.
> > Jun 8 18:20:07 localhost vmunix: [ 6.330276] wireguard: Copyright
> > (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights
> > Reserved.
>
> There should be lines like:
>
> shepherd[1]: Service 'wireguard-XXX' has been started.
>
> Perhaps they’ve been moved to a different files due to log rotation?
>
> Without these, I cannot tell what happened.
>
> >>However, the standard
> >>service constructors/destructors no longer block, and shepherd can serve
> >>multiple clients concurrently.
> >
> > I don't know, I guess wireguard uses "non-standard" constructors.
>
> Indeed, it invokes ‘wg-quick up’ and waits for completion.
>
> I suppose that command blocks until it has set up the VPN, right?
>
> If so, we’ll need to rewrite it differently.
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2022-06-09 17:17 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 [this message]
2022-06-09 20:15 ` Ludovic Courtès
[not found] ` <CAEEhgEu2nOL6bEGYxrMdNjU8_Hoex-Xm1DMf4Kxj9M4ZEZ0uRg@mail.gmail.com>
2022-06-13 9:31 ` Ludovic Courtès
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='CAEEhgEtUOiw4UyZn3_40LPrGBOTPsK36E75YL=6Fw7gsW15VzQ@mail.gmail.com' \
--to=ncdehnel@gmail.com \
--cc=53225@debbugs.gnu.org \
--cc=ludo@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).