Service Watchdog keeps monitoring services after they had been removed
-
This is very annoying :(
I logged a bug but the dev Netgate guys closed it.
I wonder if anyone found some remedy or workaround for this issue?
Thx
-
Mmm, I think your initial description of the problem missed something.
You are saying that after removing whatever package/service was being monitored is removed from the watchdog but is still throwing warnings? But cannot be removed because they are no longer shown?
If so I cannot reproduce that. When I uninstall a package the Service Watchdog entry remains. The notices are thrown because the service is obviously not longer active. However I can still remove the entry from the service watchdog.
Steve
-
@stephenw10 said in Service Watchdog keeps monitoring services after they had been removed:
Mmm, I think your initial description of the problem missed something.
You are saying that after removing whatever package/service was being monitored is removed from the watchdog but is still throwing warnings? But cannot be removed because they are no longer shown?
If so I cannot reproduce that. When I uninstall a package the Service Watchdog entry remains. The notices are thrown because the service is obviously not longer active. However I can still remove the entry from the service watchdog.
Steve
I uninstalled pfBNG before removing it from SW and was getting emails.
Then I removed dead entries for pfBNG from SW and still was getting emailsHow did you try to reproduce?
-
I tested with syslog-ng and added it as a monitored service. Then uninstalled that and continues to see alerts until I removed the entry in the watchdog.
Feb 23 22:04:00 php-cgi 60893 servicewatchdog_cron.php: Service Watchdog detected service syslog-ng stopped. Restarting syslog-ng (Syslog-ng Syslog Server) Feb 23 22:05:00 php-cgi 80216 servicewatchdog_cron.php: Service Watchdog detected service syslog-ng stopped. Restarting syslog-ng (Syslog-ng Syslog Server) Feb 23 22:05:45 php-fpm 56765 /services_servicewatchdog.php: Configuration Change: admin@172.21.16.8 (Local Database): Removed cron job for /usr/local/pkg/servicewatchdog_cron.php Feb 23 22:05:45 check_reload_status 391 Syncing firewall Feb 23 22:05:45 php-fpm 56765 /services_servicewatchdog.php: Configuration Change: admin@172.21.16.8 (Local Database): Services: Service Watchdog: deleted a service from watchdog. Feb 23 22:05:45 check_reload_status 391 Syncing firewall -
-
Let me test....
-
Same thing with pfBlocker:
Feb 23 23:10:00 php-cgi 36157 servicewatchdog_cron.php: Service Watchdog detected service pfb_dnsbl stopped. Restarting pfb_dnsbl (pfBlockerNG DNSBL service) Feb 23 23:10:00 php-cgi 36157 servicewatchdog_cron.php: Service Watchdog detected service pfb_filter stopped. Restarting pfb_filter (pfBlockerNG firewall filter service) Feb 23 23:10:58 php-fpm 361 /services_servicewatchdog.php: Configuration Change: admin@172.21.16.8 (Local Database): Services: Service Watchdog: deleted a service from watchdog. Feb 23 23:10:58 check_reload_status 391 Syncing firewall Feb 23 23:11:00 php-cgi 67345 servicewatchdog_cron.php: Service Watchdog detected service pfb_filter stopped. Restarting pfb_filter (pfBlockerNG firewall filter service) Feb 23 23:11:02 php-fpm 361 /services_servicewatchdog.php: Configuration Change: admin@172.21.16.8 (Local Database): Removed cron job for /usr/local/pkg/servicewatchdog_cron.php Feb 23 23:11:02 check_reload_status 391 Syncing firewall Feb 23 23:11:03 php-fpm 361 /services_servicewatchdog.php: Configuration Change: admin@172.21.16.8 (Local Database): Services: Service Watchdog: deleted a service from watchdog. Feb 23 23:11:03 check_reload_status 391 Syncing firewallDo you still see the log entries after removing the watchdog entries?
-
I don't want to do it on my production system, but will definitely test when the next point release is out and update you.
-
Ok, no problem. I'll wait to hear if you're able to replicate it.
