Bug #15916
closed
pfBlockerNG dnsbl daemon not able to start in CARP mode
100%
Description
pfBlockerNG dnsbl daemon not able to start in CARP mode:
CARP is created as disabled on update after applying the configuration, and service pfb_dnsbl will be listed as "stopped"
manually re-saving the CARP helps, but it gets stuck on the next pfBlockerNG update, forced or cron'd.
affected versions of pfBlockerNG: 3.2.0_10, 3.2.0_16, 3.2.0_20(devel)
logs and relevant config for dnsbl attached
Files
Updated by dylan mendez about 1 year ago
I can replicate this issue on 25.01-devel as well with known good HA sync setup. Worth mentioning the CARP VIP appears to be MASTER but it's not being detected properly as MASTER, this might be related. 
Updated by Marcos M about 2 months ago
- Status changed from New to Pull Request Review
Updated by Marcos M about 1 month ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Marcos M
- Target version set to 2.9.0
- % Done changed from 0 to 100
- Plus Target Version set to 25.11
Updated by Marcos M about 1 month ago
This should be fixed in pfBlockerNG-devel - changes have been picked to 25.11.
pfBlockerNG (non-devel) will pick up the fixes whenever it gets synced with pfBlockerNG-devel.