Hi Alex,
some systemd services are parameterized (the part after "@"). Your
systemd service file for OpenVPN takes the config name as parameter.
Which is why you have to call
systemctl start openvpn@serverA
To get the services to start on boot, try
systemctl enable openvpn@serverA
You can view the status using
systemctl status openvpn@serverA
this will also tell you where the service file is located so you can
have a look inside.
The logs are available using
journalctl -u openvpn@serverA
Regards,
Jiri
On 05/16/2018 10:16 AM, Alex K wrote:
Hi all,
I am migrating a server setup with two serer configs (serverA.conf,
serverB.conf) from Debian7 on a Debian9 server. I have removed server.conf.
When issuing systemctl start openvpn the server configs are not loaded.
I can load server configs only by issuing:
systemctl start openv@serverA
systemctl start openv@serverB
Also, what is troubling me is that on startup these configs are not
started.
What is the best way to load these configs on startup?
Thanx,
Alex
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
