I compiled OpenVPN 2.4.2 from source on Ubuntu server 16.04. This is my openvpn.service file located in /lib/systemd/system : [code][Unit] Description=OpenVPN client After=network.target [Service] Type=forking PIDFile=/var/run/openvpn/%i.pid ExecStart=/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/openvpn.pid --cd /etc/openvpn/pia/ --config Mexico.conf ExecStop=-/bin/kill -TERM $MAINPID Restart=on-failure [Install] WantedBy=multi-user.target[/code] I get this error [code]Job for openvpn.service failed because a timeout was exceeded. See "systemctl status openvpn.service" and "journalctl -xe" for details.[/code] If I run systemctl status openvpn.service I see it complaining about [code]Jun 19 04:29:33 test systemd[1]: openvpn.service: PID file /var/run/openvpn/.pid not readable (yet?) after start: No such file or directory[/code] But if I run ls -l in /var/run/openvpn I get :[code] -rw-r--r-- 1 root root 5 Jun 19 04:32 openvpn.pid[/code] But it's working since my public IP changes after that, but it changes a lot so because openvpn is restarting. How can I generate a more detailed log or fix this issue? I use pia and all PIA files are located in /etc/openvpn/pia and I want to use the Mexico server which I renamed to Mexico.conf This is my Mexico.conf file : [code]client dev tun proto udp remote mexico.privateinternetaccess.com 1198 resolv-retry infinite nobind persist-key persist-tun cipher aes-128-cbc auth sha1 tls-client remote-cert-tls server auth-user-pass login.conf comp-lzo verb 1 reneg-sec 0 crl-verify crl.rsa.2048.pem ca ca.rsa.2048.crt disable-occ [/code] login.conf is my username and password and it's in the same directory... I compiled OpenVPN following this guide here https://www.htpcguides.com/compile-latest-openvpn-from-source-on-debian-8/

I can't edit anymore so I'm posting a reply...I did more testing and found a interesting "solution" : I found this settings in a guide so I copied it and adapted to my settings : [code][Unit] Description=OpenVPN client After=network.target [Service] RuntimeDirectory=openvpn PrivateTmp=true KillMode=mixed Type=forking PIDFile=/var/run/openvpn/%i.pid ExecStart=/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/openvpn.pid --cd /etc/openvpn/pia/ --config Mexico.conf ExecReload=/bin/kill -HUP $MAINPID WorkingDirectory=/etc/openvpn Restart=on-failure RestartSec=3 ProtectSystem=yes LimitNPROC=10 DeviceAllow=/dev/null rw DeviceAllow=/dev/net/tun rw [Install] WantedBy=multi-user.target[/code] It works fine when the file is named as openvpn@openvpn.service but the same settings fail if the file is named openvpn.service... Is there a reason for this? Is there any settings here that you would change ? Why? It would be really great if someone who understands also explains why some of those are needed and they do like LimitNPROC, DeviceAllow and the others... I noticed that those settings work when named as openvpn@openvpn.service but it still give some non-fatal erros like : [code] ERROR: Linux route add command failed: external program exited with error status: 7 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this[/code]

[quote="nott240"]I compiled OpenVPN 2.4.2 from source[/quote]Please post [code]$ openvpn --version[/code]

Systemd file fails with timeout errors but still works

nott240

I compiled OpenVPN 2.4.2 from source on Ubuntu server 16.04.

This is my openvpn.service file located in /lib/systemd/system :

[Unit]
Description=OpenVPN client
After=network.target

[Service]
Type=forking
PIDFile=/var/run/openvpn/%i.pid
ExecStart=/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/openvpn.pid --cd /etc/openvpn/pia/ --config Mexico.conf
ExecStop=-/bin/kill -TERM $MAINPID
Restart=on-failure


[Install]
WantedBy=multi-user.target

I get this error

Job for openvpn.service failed because a timeout was exceeded. See "systemctl status openvpn.service" and "journalctl -xe" for details.

If I run systemctl status openvpn.service I see it complaining about

Jun 19 04:29:33 test systemd[1]: openvpn.service: PID file /var/run/openvpn/.pid not readable (yet?) after start: No such file or directory

But if I run ls -l in /var/run/openvpn I get :

 -rw-r--r-- 1 root root 5 Jun 19 04:32 openvpn.pid

But it's working since my public IP changes after that, but it changes a lot so because openvpn is restarting.

How can I generate a more detailed log or fix this issue? I use pia and all PIA files are located in /etc/openvpn/pia and I want to use the Mexico server which I renamed to Mexico.conf

This is my Mexico.conf file :

client
dev tun
proto udp
remote mexico.privateinternetaccess.com 1198
resolv-retry infinite
nobind
persist-key
persist-tun
cipher aes-128-cbc
auth sha1
tls-client
remote-cert-tls server
auth-user-pass login.conf
comp-lzo
verb 1
reneg-sec 0
crl-verify crl.rsa.2048.pem
ca ca.rsa.2048.crt
disable-occ

login.conf is my username and password and it's in the same directory...

I compiled OpenVPN following this guide here https://www.htpcguides.com/compile-latest-openvpn-from-source-on-debian-8/

nott240

I can't edit anymore so I'm posting a reply...I did more testing and found a interesting "solution" :

I found this settings in a guide so I copied it and adapted to my settings :

[Unit]
Description=OpenVPN client
After=network.target

[Service]
RuntimeDirectory=openvpn
PrivateTmp=true
KillMode=mixed
Type=forking
PIDFile=/var/run/openvpn/%i.pid
ExecStart=/usr/sbin/openvpn --daemon --writepid /var/run/openvpn/openvpn.pid --cd /etc/openvpn/pia/ --config Mexico.conf
ExecReload=/bin/kill -HUP $MAINPID
WorkingDirectory=/etc/openvpn
Restart=on-failure
RestartSec=3
ProtectSystem=yes
LimitNPROC=10
DeviceAllow=/dev/null rw
DeviceAllow=/dev/net/tun rw


[Install]
WantedBy=multi-user.target

It works fine when the file is named as openvpn@openvpn.service but the same settings fail if the file is named openvpn.service... Is there a reason for this?

Is there any settings here that you would change ? Why? It would be really great if someone who understands also explains why some of those are needed and they do like LimitNPROC, DeviceAllow and the others...

I noticed that those settings work when named as openvpn@openvpn.service but it still give some non-fatal erros like :

  ERROR: Linux route add command failed: external program exited with error status: 7
    
    WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this

TinCanTech

nott240 wroteI compiled OpenVPN 2.4.2 from source

Please post

$ openvpn --version