openvpnsrv.exe not detecting death of openvpn.exe

[jhaar]

Hi there

We had an incident over the weekend where a user reported openvpn (Win7/64bit running as a service) suddenly stopped working. They checked TaskManager? and saw openvpnsrv.exe was running, but openvpn.exe was not. The service was still marked as active

So they did a stop/start on the service and then it all came right. We have configured the "openvpn service" to autorestart after 1 minute when there's an outage, but I suspect that tracks the state of openvpnsrv.exe - not openvpn.exe? The openvpn logfile contained no explanation of what triggered his error, but EventLogs? contained a record of the event (attached)

So I tried duplicating this issue myself. If I kill openvpn.exe using taskkill (obviously when also running openvpn as a service), the same thing happens - it isn't auto-restarted.

Surely openvpnsrv.exe should be doing that? My expectation of a service is that it's always "running".

Thanks!

[Samuli Seppänen]

I don't think openvpnserv.exe does any tracking of the openvpn.exe instances it creates. It probably should, as you say. In the case it fails to autostart a particular OpenVPN instance it should also notify the admin somehow, e.g. send a system event to Windows.

[atze]

This seems to be a duplicate of #110, and in my installation this behaviour leads to openvpn tunnels not surviving hibernation (which did perfectly fine in 2.1.x), like in #71.

[Samuli Seppänen]

#71 has been reported on 2.1.4, too, so I doubt much has changed in openvpnserv.exe since then.

Closing this as a duplicate of #110