OpenVPN daemon stops working
-
It seems that the OpenVPN daemon just stops working on one of our PFsense instances.
The status page just says that it cannot connect to openvpn daemon.
There is nothing weird in the openvpn log, just normal conencted traffic and then the normal startup when I start it up manually again.
The system log says:
May 24 17:28:07 kernel pid 54591 (openvpn), jid 0, uid 0: exited on signal 11 (core dumped)
May 24 17:28:07 kernel ovpns1: link state changed to DOWNWhat could causing it, how could it be stopped and what could be done to detect it so that I do not have to manually start OpenVPN to get it to work again?
-
@Luvirini said in OpenVPN daemon stops working:
What could causing it, how could it be stopped and what could be done to detect it so that I do not have to manually start OpenVPN to get it to work again?
What =
Was terminated due to Signal 11?
Signal 11, also known as SIGSEGV (signal segmentation violation) is an error signal in Unix systems (Linux). The error appears when a program or code tries to access an invalid memory location. The operating system sends the signal 11 error to the program as a response.I presume FreeBSD is somewhat the same as Linux here.
It's a program crash. Not something an end user, like you and me, can solve.
What pfSense version ? -
@Gertjan It seems to be a known problem in 2.7.1 that is used in that one:
https://forum.netgate.com/topic/184246/openvpn-on-2-7-1-crashes-on-some-circumstances/7I apparently need to update to new version.
But yes, part of my question was: Is there something like systemd in linux to autostart services that have crashed as the crashes were not frequent so a mitigation like that could have already helped a lot. As the problem basically seems to happen overnight about once a week or two weeks,
-
@Luvirini said in OpenVPN daemon stops working:
2.7.1
?,
You've re invented the reason why "2.7.2" came out
@Luvirini said in OpenVPN daemon stops working:
to autostart services that have crashed
The system blow up tool ? This one :
? Won't help you very much.
VPn will blow up, core dumps, OpenVPN gets restarted, rinse and repeat.
After several cycles, system stability can become an issue.Just upgrade to 2.7.2 and call it a day.
Service_Watchdog is useful for system developers, so they do not have to baby-sit their "not-ready-code" all the time.
Edit : Just to motivate you : I'm using pfSense, and OpenVPN server for more then a decade. Never had it seg-fault on me.
