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
Hi,
Nathan Dehnel skribis:
> 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
>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:
Hi Nathan,
Nathan Dehnel 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
>
>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.
Hi Nathan,
Nathan Dehnel skribis:
> Just tested and Shepherd 0.9 does not fix this issue.
Could you be more specific? Specifically, could you share
/var/log/messages for the parts related to Wireguard?
> On Mon, Jan 17, 2022 at 7:48 AM Ludovic Courtès wrote:
[...]
>> One command sent to
Just tested and Shepherd 0.9 does not fix this issue.
On Mon, Jan 17, 2022 at 7:48 AM Ludovic Courtès wrote:
>
> Hi,
>
> Nathan Dehnel skribis:
>
> >>What do you mean by “freezing”? Does ‘herd status’ and similar commands
> > block forever?
> > Yes
> >
> >>Requests in the Shepherd are
Hi,
Nathan Dehnel skribis:
>>What do you mean by “freezing”? Does ‘herd status’ and similar commands
> block forever?
> Yes
>
>>Requests in the Shepherd are currently handled sequentially. So if you
> issue several ‘herd restart’ commands, they’ll be processed one at a
> time. This is
>What do you mean by “freezing”? Does ‘herd status’ and similar commands
block forever?
Yes
>Requests in the Shepherd are currently handled sequentially. So if you
issue several ‘herd restart’ commands, they’ll be processed one at a
time. This is usually okay because ‘start’ commands are
Hi,
Nathan Dehnel skribis:
> When dns is specified, wireguard runs wg-quick, which runs resolvconf,
> which runs /run/current-system/profile/bin/herd restart, which causes
> shepherd to freeze because I guess it doesn't like being given
> multiple start commands at once. I'm not sure how to fix
When dns is specified, wireguard runs wg-quick, which runs resolvconf,
which runs /run/current-system/profile/bin/herd restart, which causes
shepherd to freeze because I guess it doesn't like being given
multiple start commands at once. I'm not sure how to fix it.
11 matches
Mail list logo
