Problem starting openvpn-client@service.service
Posted: Thu Dec 06, 2018 4:18 pm
Hello
I'm new to the forum and a newbie to VPN's - bear with me.
I've just installed the latest Openvpn on Ubuntu 16.04 using systemd. Two questions to start:
1) Do I need to start the server service to setup a simple VPN through a provider or whatever?
2) I assume the client service has to be running, at startup, to setup a VPN using a connection manager like Connman or Networkmanger?
I assumed that 2) is true and enabled the service, but get the following errors(journalctl -xe):
openvpn-client@service.service - OpenVPN tunnel for service
Loaded: loaded (/lib/systemd/system/openvpn-client@.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-12-06 15:58:28 GMT; 8s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/w ... n24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 9018 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config %i.conf (code=exited, status=210/CHROOT)
Main PID: 9018 (code=exited, status=210/CHROOT)
Dec 06 15:58:28 cliffhangers systemd[1]: Starting OpenVPN tunnel for service...
Dec 06 15:58:28 cliffhangers systemd[9018]: openvpn-client@service.service: Failed at step CHROOT spawning /usr/sbin/openvpn: No such file or directory
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Main process exited, code=exited, status=210/CHROOT
Dec 06 15:58:28 cliffhangers systemd[1]: Failed to start OpenVPN tunnel for service.
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Unit entered failed state.
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Failed with result 'exit-code'
Any ideas here?
I thought this might have been connected to the 'spawn' package. But it seems not. If I run '/usr/sbin/openvpn' from the command line it's functional.
Thanks
Cliff
I'm new to the forum and a newbie to VPN's - bear with me.
I've just installed the latest Openvpn on Ubuntu 16.04 using systemd. Two questions to start:
1) Do I need to start the server service to setup a simple VPN through a provider or whatever?
2) I assume the client service has to be running, at startup, to setup a VPN using a connection manager like Connman or Networkmanger?
I assumed that 2) is true and enabled the service, but get the following errors(journalctl -xe):
openvpn-client@service.service - OpenVPN tunnel for service
Loaded: loaded (/lib/systemd/system/openvpn-client@.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-12-06 15:58:28 GMT; 8s ago
Docs: man:openvpn(8)
https://community.openvpn.net/openvpn/w ... n24ManPage
https://community.openvpn.net/openvpn/wiki/HOWTO
Process: 9018 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind --config %i.conf (code=exited, status=210/CHROOT)
Main PID: 9018 (code=exited, status=210/CHROOT)
Dec 06 15:58:28 cliffhangers systemd[1]: Starting OpenVPN tunnel for service...
Dec 06 15:58:28 cliffhangers systemd[9018]: openvpn-client@service.service: Failed at step CHROOT spawning /usr/sbin/openvpn: No such file or directory
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Main process exited, code=exited, status=210/CHROOT
Dec 06 15:58:28 cliffhangers systemd[1]: Failed to start OpenVPN tunnel for service.
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Unit entered failed state.
Dec 06 15:58:28 cliffhangers systemd[1]: openvpn-client@service.service: Failed with result 'exit-code'
Any ideas here?
I thought this might have been connected to the 'spawn' package. But it seems not. If I run '/usr/sbin/openvpn' from the command line it's functional.
Thanks
Cliff