I proposed to add the '+' in the supported releases to avoid a failure
while users try to reload the service:
$ sudo systemctl reload openvpn@server
Job for openvpn@server.service failed because the control process exited with
error code.
See "systemctl status openvpn@server.service" and "journalctl -xe" for details.
$ echo $?
1
$ sudo systemctl status openvpn@server
● openvpn@server.service - OpenVPN connection to server
Loaded: loaded (/lib/systemd/system/openvpn@.service; indirect; vendor
preset: enabled)
Active: active (running) (Result: exit-code) since Tue 2020-05-26 17:11:33
-03; 24s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 9548 ExecReload=/bin/kill -HUP $MAINPID (code=exited,
status=1/FAILURE)
Main PID: 9528 (openvpn)
Status: "Initialization Sequence Completed"
Tasks: 1 (limit: 1152)
CGroup: /system.slice/system-openvpn.slice/openvpn@server.service
└─9528 /usr/sbin/openvpn --daemon ovpn-server --status
/run/openvpn/server.status 10
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: GID set to nogroup
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: UID set to nobody
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: MULTI: multi_init
called, r=256 v=256
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: IFCONFIG POOL:
base=10.8.0.4 size=62,
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: IFCONFIG POOL LIST
May 26 17:11:33 openvpn-reload-bionic ovpn-server[9528]: Initialization
Sequence Completed
May 26 17:11:49 openvpn-reload-bionic systemd[1]: Reloading OpenVPN connection
to server.
May 26 17:11:49 openvpn-reload-bionic kill[9548]: kill: (9528): Operation not
permitted
May 26 17:11:49 openvpn-reload-bionic systemd[1]: openvpn@server.service:
Control process exite
May 26 17:11:49 openvpn-reload-bionic systemd[1]: Reload failed for OpenVPN
connection to serve
This error (it returns 1) might confuse users. However, as you can see above,
even when the reload command fails the service itself remains active and
running. The same happens if we add the '+', but the reload command succeeds
(returns 0).
Anyway, I'll prepare a MP to drop the reload support in Groovy while we
decide if it worth to SRU a "fix" for this to the supported releases.
** Changed in: openvpn (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu)
Status: Triaged => In Progress
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
** Changed in: openvpn (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: openvpn (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: openvpn (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868127
Title:
OpenVPN will not reload due to misconfigured .service file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1868127/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
