OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: myksto on May 08, 2019, 04:00:44 pm

Title: Open VPN daemon doesn't start after firewall reboot
Post by: myksto on May 08, 2019, 04:00:44 pm
I have two Openvpn servers in the same firewall: OPN1 and OPN2.
Sometimes after a firewall reboot both deamons don't come up and in dashboard they're red. If I try to restart them they don't and logs says that:
"openvpn[76450]: Exiting due to fatal error;
 openvpn[76450]: Cannot open TUN/TAP dev /dev/tun1: Device busy (errno=16)
 openvpn[76450]: TUN/TAP device ovpns1 exists previously, keep at program end"

I found an old post https://forum.opnsense.org/index.php?topic=6376.0 and there I found the solution to find and kill processes. In that post a bug was opend at Github but I was not able to understand whether the bug had been correct or not.

Is it known why this happens?
Is there a more simply way to make Open VPN deamons come up after a simple firewall reboot (for example for a system update)?

Thanks a lot.

Best regards,
Michele
Title: Re: Open VPN daemon doesn't start after firewall reboot
Post by: franco on May 09, 2019, 09:24:58 am
Hi Michele,

There is a fix planned via https://github.com/opnsense/core/issues/3223

Long story short, the service is running (device busy) but the PID file wasn't correctly written yet... in 19.1.9 we will wait for the OpenVPN instance PID to appear 10 seconds.

Note this will *not* make 19.1.8 early next week.


Cheers,
Franco
Title: Re: Open VPN daemon doesn't start after firewall reboot
Post by: myksto on May 10, 2019, 03:22:28 pm
Hi Franco,
thanks for reply.

I tried to apply patch with command "opnsense-patch c217bee" but console return me this:  "1 out of 1 hunks failed while patching etc/inc/plugins.inc.d/openvpn.inc".

Am I doing something wrong?

Then sorry but I did't understand what you wrote at the end of your post: you mean patch will be applied with the 19.1.9 opnsense update?

Thanks and cheers,
Michele.
 
Title: Re: Open VPN daemon doesn't start after firewall reboot
Post by: franco on May 10, 2019, 07:23:26 pm
opnsense-patch doesn't always work. We've done a lot of work in OpenVPN and there is no stable patch yet.

We'll ship the fix in 19.1.9. As it's a GUI glitch and not an operation issue I hope the wait is ok.


Cheers,
Franco
Title: Re: Open VPN daemon doesn't start after firewall reboot
Post by: myksto on May 13, 2019, 10:44:35 am
Ok Franco.
I will wait for the fix in 19.1.9 release.

Thanks a lot.

Cheers,
Michele.
Title: Re: Open VPN daemon doesn't start after firewall reboot
Post by: myksto on June 13, 2019, 09:11:29 am
Hi Franco.
Just to let you know that after 19.1.9 update openvpn status is still down on the GUI.

When I first rebooted the firewall it seemed to be ok but after a second reboot the problem is still there. I had to find the process with a "ps auxw | grep openvpn", kill it and then restart openvpn server form the gui.

Thanks a lot.

Cheers,
Michele.