pinxi: (cannot edit my posts to replace inxi output with current)
I start OpenVPN from terminal.
After 2020-08-28 update update-resolve-conf fails, OpenVPN log at verb 4:
Fri Aug 28 15:46:49 2020 us=646697 /etc/openvpn/up.sh tun0 1500 1585 10.50.0.15 255.255.0.0 init
+ run /etc/openvpn/update-resolv-conf
dhcp-option DNS 10.50.0.1
/usr/lib/resolvconf/libc.d/avahi-daemon: line 31: kill: (434) - Operation not permitted
+ '[' 1 -ne 0 ']'
+ echo '/etc/openvpn/update-resolv-conf Failed with exit code 0'
/etc/openvpn/update-resolv-conf Failed with exit code 0
+ return 1
Fri Aug 28 15:46:49 2020 us=696834 WARNING: Failed running command (--up/--down): external program exited with error status: 1
Fri Aug 28 15:46:49 2020 us=696857 Exiting due to fatal error
I never saw avahi-deamon in OpenVPN logs.
if [ -s "$avahi_daemon_pidfile" ]; then
kill -HUP $(cat "$avahi_daemon_pidfile")
Help troubleshooting appreciated,
now using update-systemd-resolved:
Works fine but still wondering why the previous solution failed…
systemd runs at root level, so the kill that was failing:
now just works.
Also, in the future, please mark a solution like this:
so that the next person that has the exact same problem you just had will benefit from your post as well as your question will now be in the “solved” status.
Using update-systemd-resolved doesn’t solve the problem with update-resolv-conf.
But yes, it is a solution from user point of view.
Coming back to this:
So does OpenVPN and it used to work fine before the 2020-08-28 update:
root 347026 0.0 0.1 19460 10620 ? Ss 17:37 0:00 /usr/bin/openvpn --config client.conf
After a shutdown last night it doesn’t work anymore today.
I can ping:
but Firefox is unable to resolve DNS the same for dig.
Did a pre update restore, working fine.
Will wait for next update.
openresolv added support to notify avahi-daemon and mdnsd of resolv.conf changes last month.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.