OPENVPN Server dies after 2.1.2 update, logs enclosed
-
Just started happening to me with 2.1.2-RELEASE (amd64). Wasn't even logged into PfSense. Abruptly i started getting the same message as others, by txt, so opened PfSense and found OpenVpn service was down and cron was trying to restart it. Every restart produces the same message and OpenVpn won't start so I removed it from Cron to keep from getting annoyed by the repeating error message. I'll try a cron 4am reboot and hope it resolves itself.
-
Found another forum post suggesting ps aux to find the ovpn PID then did a Kill "PID#" to stop the lost instance, then OpenVpn would start which caused NTP service to crash, once restarted caused ntop to crash, once restarted all appears stable. After this odd behavior I'll be rebooting next opportunity. Solved for now…
-
Mine does the same with NTP as you described (after killing/restarting ovpn), but reloading that status page "fixes" NTP.
-
OpenVPN died again this afternoon. Service watchdog was not able to start it despite repeated attempts. Had to reboot to get it working again. So long to the countdown before another crash.
Is anyone acknowledging this issue?
-
OP's logs seem to show gateway status going down and back up. When a gateway comes back up, the VPNs associated with it are restarted. Fix your gateway monitoring (set to an IP that replies reliably), or disable it, and it won't do that.
-
Gateway monitoring is disabled since initial install. It's not the case with gateway going down. I have re-checked again and the gateway has been running fine with no ping drops for days.
-
Something is triggering that code path. Maybe a WAN reconnection if a dynamic WAN type?
-
I'd like to add that I too have this problem, but it doesn't start until I max out the outbound bandwidth of my OpenVPN connection (which is used exclusively by OpenVPN)
This is what the bandwidth graph looks like. Some data goes through briefly, then the crash and repeat, like what is seen in the OP's logs.
Also, the 'trick' to kill the OpenVPN process and restart it doesn't fix the problem for me.
-nb -
Help - same issue. Once I max out my network connection OpenVPN crashes. I have tried 2.11, 2.12, and 2.13 all of these versions appears by have the problem. I have had very good success with 2.1 working with no problems and tried a clean installed 2.13, but once the network is maxed OPENVPN/connection crashes. Any assistance to fix this issue would be greatly appreciate. I really want to transition to 2.1.3, but not at the expense of OpenVPN and stability.
-
It's not actually crashing from anything anyone's shown here. Something is triggering it to restart, seemingly most likely a gateway being flagged as down. Does anything in the gateways log correlate to the VPN reconnecting?
-
I've noticed I've started to get resets on pfsense connecting out as a openvpn client
(didn't notice any problems on incoming connections but they may occur)
not sure if it's the same things as discussed in this thread
actually, the outgoing client connection seem to be up eventhough it's listed as down,
I checked and traffic seems to flow ok out through it, but it's listed as down and if I restart it it only works occasionally (reboot better) and then it's listed as up,I have a faint memory it worked to restart openvpn earlier but as stated above dont seem to work anymore
-
Running snort?
For the last 24 hours one out of three boxes snort is killing one of two openVPN tunnels (both clients) from this box, no idea why…
 -
no snort, it's on 4G memcard btw,
I have 'only' NUT (UPS addon, disabled) and crond packages installed,I have /had earlier similar setup to
http://doc.pfsense.org/Create-OpenVPN-client-to-TUVPNcom.pdf
(including the crond part at the end) but crond part was inactive lost/disabled since a few upgrades ago -
I just had the same problem with fresh installation of 2.2 after running with no problems for about two weeks. No idea what triggered this behavior. I had to stop OpenVPN, go to shell and kill processes.
Any solution to this?
-
I just had the same problem
There are at least 2 if not 3 completely different and unrelated problems described by others in this thread. At least one where Snort was blocking the VPN, at least one other that's probably from delayed DNS resolution and the client getting started multiple times (which is fixed in 2.2), and probably different unrelated ones for others. Please start a new thread with specifics on what you're seeing happen, and what OpenVPN logs you're getting at the time.