Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another app is currently holding the xtables lock. #41

Open
pogman-code opened this issue Jan 19, 2021 · 0 comments
Open

Another app is currently holding the xtables lock. #41

pogman-code opened this issue Jan 19, 2021 · 0 comments

Comments

@pogman-code
Copy link

Hi,
Lately I have the following error when starting an openvpn client using vpnfailsafe.sh as up/down script:

Jan 19 09:39:17 openvpn[39322]: /etc/openvpn/vpnfailsafe.sh tun0 1500 1553 AAA.BBB.CCC.DDD 255.255.255.0 init
Jan 19 09:39:17 openvpn[39491]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
Jan 19 09:39:17 openvpn[39391]: /etc/openvpn/vpnfailsafe.sh:114: `iptables -N "VPNFAILSAFE_$*"' returned 4
Jan 19 09:39:17 openvpn[39322]: WARNING: Failed running command (--up/--down): external program exited with error status: 4
Jan 19 09:39:17 openvpn[39322]: Exiting due to fatal error

I am no iptables expert but as far as I understand there is a race condition somewhere and it suggests to add -w flag to (all?) iptables calls.

Should I do that to the script or is there a more elegant explanation/solution to this issue?

Thanks!

NB: As I was looking for an answer I stumbled upon this blog post that looks pretty close to my problem: https://utcc.utoronto.ca/~cks/space/blog/linux/IptablesWOptionFumbles

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant