** Also affects: openvpn
Importance: Undecided
Status: New
** Project changed: openvpn => ubuntu-release-notes
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1771650
Title:
@Fanar does comment #15 solve your case? If yes, I can add a release
notes task to this bug and update
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes mentioning this change
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
The client/server @ units need a config file, otherwise they cannot be
activated. I'm not sure what the main openvpn.service one is for now,
though.
Ah, it does nothing apparently:
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/true
ExecReload=/bin/true
WorkingDirectory=/etc/openvpn
Assuming you have a config file called /etc/openvpn/server/myconfig, can
you try:
systemctl start openvpn-server@myconfig
That should trigger the openvpn-server@ service file, which will replace %i in
the Exec line below with what's after @ in the systemctl start command:
This needs further investigation, because the package does ship service
files for server and client:
# dpkg -L openvpn|grep service
/lib/systemd/system/openvpn-client@.service
/lib/systemd/system/openvpn-server@.service
/lib/systemd/system/openvpn.service
/lib/systemd/system/openvpn@.service
We
See this upstream change:
https://github.com/OpenVPN/openvpn/commit/28bd79ac980488dbfce2e8136287e38c6f35a043
I believe all you had to do was place the config file in
/etc/openvpn/server or /etc/openvpn/client, then the systemd units would
pick it up automatically.
Could you please verify that?
