diff options
| author | Dmitry Ilvokhin <d@ilvokhin.com> | 2026-01-04 15:59:47 +0000 |
|---|---|---|
| committer | Dmitry Ilvokhin <d@ilvokhin.com> | 2026-01-04 15:59:47 +0000 |
| commit | d83d53c7e8e5c218dd19ef9a0cfe3941820fdf96 (patch) | |
| tree | e999db8254211d10ad400162b41339b460089c19 /hosts.yml | |
| parent | b6c70ab314b7ab6dd94cc7b796b67f89f3e5ea50 (diff) | |
| download | infra-d83d53c7e8e5c218dd19ef9a0cfe3941820fdf96.tar.gz infra-d83d53c7e8e5c218dd19ef9a0cfe3941820fdf96.tar.bz2 infra-d83d53c7e8e5c218dd19ef9a0cfe3941820fdf96.zip | |
Wait for /run/xtables.lock for wireguard rules
When box is restarted seems like there is a race to take iptables lock
file and some units can not start because of that.
In the log error looks like this.
Can't lock /run/xtables.lock: Resource temporarily unavailable
Another app is currently holding the xtables lock. Perhaps you want
to use the -w option?
Take iptables suggestion and wait for the xtables lock.
Downside is if something is not going to release the lock, then we stall
forever.
Diffstat (limited to 'hosts.yml')
0 files changed, 0 insertions, 0 deletions