Run openvpn server at boot

[WarheadsSE]

Dude, we're talking about running/enabling the systemd service.

Yes, when you manually call openvpn you need to specify the whole path.

"restorecon" seems to an item from SElinux. (http://fedoraproject.org/wiki/SELinux/restorecon)

[Socaltom]

$this->bbcode_second_pass_quote('gcp900', '
')
$this->bbcode_second_pass_code('', '[root@alarmpi ~]# openvpn server.conf
Options error: In [CMD-LINE]:1: Error opening configuration file: server.conf
Use --help for more information.')

So I don't know what's wrong. Anyway, it happens the same in all computers I have installed openvpn as a client. I have to specify the route of the conf files even being in the default route (/etc/openvpn).
[/code]

$this->bbcode_second_pass_quote('', 'T')his is normal behaviour if you call openvpn from the command line. The proper command is

Code: Select all
systemctl start openvpn@server.service



This tells systemd to start openvpn and the location is set in the service file to /etc/openvpn

[Socaltom]

The reason it probably didn'tt start is because when it starts it wants to write a pid file ( I think this is so it can tell if its already running). In your case, the PID file was already there, so it refused to try and start.

go to /run and delete any openvpn*.pid files and try again.

Tom

[gcp900]

$this->bbcode_second_pass_code('', '[root@alarmpi ~]# cd /run
[root@alarmpi run]# ls
dbus dmeventd-server log mount sshd.pid tmpfiles.d user uuidd
dmeventd-client lock lvm nscd systemd udev utmp
')

That's what I have inside /run. I don't see any openvpn.pid file.

But now you've said that I remember that the first time I used systemctl with openvpn it worked in the following reboot, after that it didn't.

[Socaltom]

the only other thing I can think of is that for some reason it doesn't have rights to write the pid file.
do ls -l, in /run
It's "enabled" so it will try and start openvpn on a reboot.

Tom

[gcp900]

$this->bbcode_second_pass_code('', 'drwxr-xr-x 2 root root 60 Mar 7 19:31 dbus
prw------- 1 root root 0 Jan 1 1970 dmeventd-client
prw------- 1 root root 0 Jan 1 1970 dmeventd-server
drwxr-xr-x 5 root root 100 Jan 1 1970 lock
drwxr-xr-x 2 root root 40 Jan 1 1970 log
drwxr-xr-x 2 root root 60 Jan 1 1970 lvm
drwxr-xr-x 2 root root 40 Jan 1 1970 mount
drwxr-xr-x 2 root root 40 Jan 1 1970 nscd
-rw-r--r-- 1 root root 4 Mar 7 19:31 sshd.pid
drwxr-xr-x 15 root root 380 Mar 7 19:31 systemd
drwxr-xr-x 2 root root 60 Jan 1 1970 tmpfiles.d
drwxr-xr-x 7 root root 160 Mar 8 21:19 udev
drwxr-xr-x 3 root root 60 Mar 8 21:19 user
-rw-rw-r-- 1 root utmp 1920 Mar 17 12:15 utmp
drwxr-xr-x 2 uuidd uuidd 40 Jan 1 1970 uuidd')

That's what I've got. Do you see anything?

[gcp900]

Misteriously It is working right now...

Thank for the support!!