Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)
-
After upgrading to v7.2.0 yesterday afternoon, I logged in this morning to check memory/cpu and noticed the cpu was running higher than v2.6.0
After searching the logs I found this message repeating every min.
Aug 16 19:53:00 php-cgi 93905 servicewatchdog_cron.php: Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)
Aug 16 19:52:00 php-cgi 56293 servicewatchdog_cron.php: Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)
Aug 16 19:51:00 php-cgi 83780 servicewatchdog_cron.php: Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)
Aug 16 19:50:00 php-cgi 44661 servicewatchdog_cron.php: Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)
Aug 16 19:49:00 php-cgi 77391 servicewatchdog_cron.php: Service Watchdog detected service dnsbl stopped. Restarting dnsbl (pfBlockerNG DNSBL Web Server)I went back in the log and found this started on 8/16 after 19:45 hr MDT (so not due to yesterdays update).
BIOS Vendor: AMI
Version: L43 v01.09
Release Date: Mon Aug 28 2017
Version 2.7.0-RELEASE (amd64)
built on Wed Jun 28 03:53:34 UTC 2023
FreeBSD 14.0-CURRENT
CPU Type AMD RX-427BB with AMD Radeon(tm) R7 Graphics
Current: 1400 MHz, Max: 2700 MHz
4 CPUs: 1 package(s) x 4 core(s)
AES-NI CPU Crypto: Yes (active)
QAT Crypto: NoDisk used: 2.5G
Disk size: 447GThoughts on why this might have started on 8/16?
Thanks,
Craig
-
Upvote. I am also having this problem. A post from 2022 (which I cannot find now) suggested that the port setting at https://!PADDRESS/pfblockerng/pfblockerng_dnsbl.php DNSBL Webserver Configuration was the issue, as the ports used by dnsbl must not be used by any other service; I did not see that the default posts were in use other than by dnsbl, however.
-
From what I know, Watchdog shouldn't be used on pfB services or Unbound because it will screw up the updates when pfB bounces those services. Watchdog is a brute force program w/o any built-in intelligence.
-
@provels - Thanks for your suggestion, however I wouldn't have known there was something miss-configured without monitoring the processes and attempting to restart.
In looking at the log and the actual process name, I found the "root cause" of Watchdog attempting to restart things, the process name changed:
Restarting dnsbl (pfBlockerNG DNSBL Web Server)
Actual process: "pfBlockerNG DNSBL service" - pfb_dnsbl
So, at some point this change/update caused Watchdog to think a process wasn't running, and attempting to restart every min.
Problem solved!
pfBlockerNG - v 3.2.0_6
-
Monitor Guy, thank you, exactly right. I deleted the old dnsbl line from Service Watchdog
dnsbl pfBlockerNG DNSBL Web Serverand added
pfb_dnsbl pfBlockerNG DNSBL serviceand problem solved! No more messages every minute.
