Dear Maintainer,

When I check the journal log I see a lot of errors.
It seems like there is a file missing to start the VPN.
But when I start the VPN all works normal (my vpn also uses the same public dns services)

okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Service RestartSec=5s expired, scheduling restart.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Scheduled restart job, restart counter is at 1207.
okt 09 21:08:37 laptop systemd[1]: Stopped OpenVPN connection to update-systemd-resolved.
okt 09 21:08:37 laptop systemd[1]: Starting OpenVPN connection to update-systemd-resolved...
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: --up script fails with '/etc/openvpn/scripts/update-systemd-resolved': No such file or directory (errno=2)
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: Please correct this error.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Use --help for more information.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: Failed with result 'exit-code'.
okt 09 21:08:37 laptop systemd[1]: Failed to start OpenVPN connection to update-systemd-resolved.

Thank you for the bug report, Johan.

Could there be something with the configuration on your side?
update-systemd-resolved is installed under /etc/openvpn not /etc/openvpn/scripts

Thanks,
Eugene

Hi Eugene,

Thanks for the quick reply.

I imported a ovpn file but not to my knowledge I configured the path.
Also when I look in the network manager of the VPN tools I can't find
anything related to this.

But when I look at the file: /etc/openvpn/update-systemd-resolved.conf
That was installed by package openvpn-systemd-resolved it contains the
script path.

Here is the output of the file that was installed:

#/etc/openvpn/update-systemd-resolved.conf:
script-security 2
setenv PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
up /etc/openvpn/scripts/update-systemd-resolved
up-restart
down /etc/openvpn/scripts/update-systemd-resolved
down-pre

Is this a package error or a configuration error of the file?

Thanks,
Johan

Thank you for the bug report, Johan.

Could there be something with the configuration on your side?
update-systemd-resolved is installed under /etc/openvpn not
/etc/openvpn/scripts

Thanks,
Eugene

I see. I think the problem comes from the package.
The previous version of the package (1.3.0-2) indeed installed
/etc/openvpn/update-systemd-resolved.conf, but now this conffile is
installed into /usr/share/doc/openvpn-systemd-resolved/ just for
reference. It should be safe to remove
/etc/openvpn/update-systemd-resolved.conf for you to get rid of
journal log errors.

Eugene

Yes this solved my warnings. Should this be done by the package? Just
from a upgrade perspective for other users.

Great!
Well, it's not really an option to remove a conffile (previously
installed into /etc) on package upgrade. Some user might have actually
taken it into use.

Hello,

between yesterday on today I was dealing with setting up the up/down scripts in a openvpn client config file and it totally escaped me that in the upstream documentation it uses /etc/openvpn/scripts/ as location of the script while this package is installed one level higher in /etc/openvpn/, i realized it after some debugging.

If the file is to remain in /etc/openvpn/ (as it should), would it be possible to symlink it upon installation in /etc/openvpn/scripts too? This would avoid confusion. Or at least add some documentation noting clearly the difference in path.

Hope this is useful feedback :)

Hi,

I ran into this confusion while setting it up today.  The 1.3.0-5 package in Debian Trixie has misleading documentation about the script's location.

The README.gz and update-systemd-resolved.conf in /usr/share/doc/openvpn-systemd-resolved both refer to the script in /etc/openvpn/scripts/, but the actual script is in /etc/openvpn/.

I think it would be a good idea to patch these documentation files to reflect the correct location.

Thanks,

Mark

It is, but that needs some planning. dpkg-maintscript-helper has an
rm_conffile mode. I don't know whether it makes sense to use that for a
conffile that was removed in a previous version of the package.

Greetings
Marc

It is, but that needs some planning. dpkg-maintscript-helper has an
rm_conffile mode. I don't know whether it makes sense to use that for a
conffile that was removed in a previous version of the package.

Greetings
Marc