I tried to reproduce this in a fresh VM with:
sudo cp /usr/share/doc/openvpn/examples/sample-config-files/static-home.conf
/etc/openvpn/client1.conf
sudo cp /usr/share/doc/openvpn/examples/sample-config-files/static-office.conf
/etc/openvpn/client2.conf
sudo sed -i '/AUTOSTART.*"all"/ s/^#//' /etc/default/openvpn
sudo systemctl daemon-reload
sudo service openvpn restart
and it works as expected: "systemctl status openvpn@*" shows me that I
got openvpn@client1.service and openvpn@client2.service. Of course they
fail to start in my scenario as the example files use IP addresses
1.2.3.4 and similar, but the generator and startup works fine.
In your case openvpn@client.service looks strange -- do you actually
have a /etc/openvpn/client.conf file? This error message
May 1 11:45:39 ovpn-client[26561]: Options error: In [CMD-LINE]:1: Error
opening configuration file: /etc/openvpn/client.conf
sounds like it either exists and is invalid, or it does not exist. Can
you please give me the output of
ls -lR /etc/openvpn/*.conf
?
** Changed in: openvpn (Ubuntu)
Status: New => Incomplete
** Summary changed:
- AUTOSTART value is ignored in startup script
+ creates failing openvpn@client.service unit
--
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.service unit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/1450762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
