Watchdog restarting OpenVPN client that does not exist every minute



  • Not sure whether this should be in here or in the OpenVPN section..

    I am seeing this error in System Log every minute on the dot.

    Nov 27 08:09:00 php-cgi servicewatchdog_cron.php: Service Watchdog detected service openvpn stopped. Restarting openvpn (OpenVPN client: PIA US Silicon Valley)
    Nov 27 08:08:00 php-cgi servicewatchdog_cron.php: Service Watchdog detected service openvpn stopped. Restarting openvpn (OpenVPN client: PIA US Silicon Valley)
    Nov 27 08:07:00 php-cgi servicewatchdog_cron.php: Service Watchdog detected service openvpn stopped. Restarting openvpn (OpenVPN client: PIA US Silicon Valley)
    Nov 27 08:06:00 php-cgi servicewatchdog_cron.php: Service Watchdog detected service openvpn stopped. Restarting openvpn (OpenVPN client: PIA US Silicon Valley)

    The odd thing is I don't even have a client named that, it was removed long ago, and it seems to be causing issues when connected to a VPN Provider.

    Connection seems to stay connected going off connection time on dashboard. If I'm downloading a large file I see no noticeable drop in speed, let alone a dropout, but roughly every minute, DNS stops resolving and I can't ping the DNS servers by name or IP (Or any address for that matter)

    I have written a looping bash script to check this, and the time stamps seem to be roughly every minute give or take a few seconds.

    My internet connection is rock solid, so that is not an issue.

    I see the same behavior regardless of which VPN provider and which DNS servers I use.

    I have an OpenVPN server running so I can connect remotely, it is working with no issues whatsoever.

    Any help would be much appreciated.


  • Rebel Alliance Developer Netgate

    The Service Watchdog package only does what it is told to do. If it's checking that client, it's because it's been configured to do that. Look under Services > Service Watchdog and see what it's set for.

    Does that OpenVPN client still show on Status > Services?



  • I have just noticed there was actually an entry in service watchdog to restart the above mentioned client.

    That client had been deleted a while ago, but watchdog is still trying to restart it, even though it doesn't exist, so I can see why its giving the error now.

    I have changed watchdog to the current client, and now its not throwing those errors.

    Now that is sorted, but I'm still having what seems to be DNS issues roughly every minute when connected to the VPN though.