I found a solution for this and wanted to post in case someone else came
across it. OpenVPN stopped using /etc/default/openvpn for defaults after
switching to systemd, even though the file /etc/default/openvpn may
still be there (As it is on Debian 9 still). To configure defaults for
openvpn on sys
> this part of code was never reached when invoking
> sudo /etc/init.d/openvpn start
Yes, it's not supposed to. openvpn ships systemd units, so the init.d
script isn't getting run (and if you try to call it manually it diverts
to essentially calling "systemctl start openvpn").
--
You received t
Well,
this part of code was never reached when invoking
sudo /etc/init.d/openvpn start
case "$1" in
start)
log_action_begin_msg "Starting $DESC"
# first create /run directory so it's present even
# when no VPN are autostarted by this script, but later
# by systemd openvpn@.service
mk
Well, I would have liked to know why it was failing, but I suppose the
purging destroyed all the evidence now. Closing, thanks!
** Changed in: openvpn (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
sudo apt-get purge openvpn
sudo apt-get install openvpn
fixed the problem
this report can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450762
Title:
creates failing openvpn@client.ser
For some reason commands:
sudo /etc/init.d/openvpn start
sudo /etc/init.d/openvpn restart
are not working,
but
sudo systemctl daemon-reload
sudo service openvpn restart
are
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
