** Description changed:
+ [Impact]
+
+ The command 'systemctl reload openvpn @ $ foo' is broken for a while and
+ no one have reported that. Users should not be using it a lot. After
+ some investigation we notice the restart command does basically the same
+ thing, and users should be using rest
** Changed in: openvpn (Ubuntu Bionic)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Eoan)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
** Changed in: openvpn (Ubuntu Focal)
Assignee: (unassigned) => Lucas Kanashiro (lucaska
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openvpn/+git/openvpn/+merge/384724
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openvpn/+git/openvpn/+merge/384725
** Merge proposal linked:
https://code.launchpa
I brought more people into this discussion and we decided to drop the
reload support from the stable/supported releases since it is already
broken and the restart does basically the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This bug was fixed in the package openvpn - 2.4.9-2ubuntu2
---
openvpn (2.4.9-2ubuntu2) groovy; urgency=medium
* Drop reload support from systemd unit files (LP: #1868127)
-- Lucas Kanashiro Tue, 26 May 2020 19:04:33
-0300
** Changed in: openvpn (Ubuntu)
Status: In Progr
I'd like to mention that `systemctl $action openvpn@$foo` is using the
legacy systemd unit.
On 18.04 and newer, you are better off moving your config to
/etc/openvpn/client or /etc/openvpn/server and use corresponding and
modern systemd units: openvpn-client@$foo and openvpn-server@$foo
--
You r
After a discussion with a colleague I think we should leave it as is in
the supported/stable releases (I already fixed it in Groovy, it should
land in the archive soon). The rationale is: even if the reload command
fails the service keeps active and running, the proposed solutions would
not fix the
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/openvpn/+git/openvpn/+merge/384585
--
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 n
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 "journal
I'm not sure there's even any point to adding the '+': an error will occur
either way, whether it's in kill or in OpenVPN. At least when it appears
from kill it's obvious something went wrong (even if it's not obvious
what...).
Personally I think removing reload is the right call going forward - h
Executing the ExecReload= command with full privileges (adding '+')
indeed fixes the reload failure (I ran my tests in a Bionic and Focal
VMs but it should apply to the other releases):
May 26 10:01:41 openvpn-reload kill[1764]: kill: (1738): Operation not
permitted
I mean the command 'systemctl
** Also affects: openvpn (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: openvpn (Ubuntu Bionic)
That is a very good point. I never noticed it but it looks like my
OpenVPN is actually failing to reload, exiting, and being restarted by
systemd. It looks like I'll need to modify my 'overlay' service to use
SIGUSR1 instead.
--
You received this bug notification because you are a member of Ubunt
** Changed in: openvpn (Ubuntu)
Status: New => Triaged
--
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 notif
** Tags added: server-next
--
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:
http
The "ExecReload=+/bin/kill" way of reloading without needing extra caps
seems sensible. That said, I'm wondering what's the use case for a
reload instead of a restart as man openvpn(8) describes what happens on
SIGHUP:
SIGNALS
SIGHUP Cause OpenVPN to close all TUN/TAP and network connections, re
(PS: issue also exists in 2.4.7-1ubuntu2)
--
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
17 matches
Mail list logo
