Bug #15916: pfBlockerNG dnsbl daemon not able to start in CARP mode - pfSense Packages - pfSense bugtracker

Actions

Copy link

Bug #15916

open

pfBlockerNG dnsbl daemon not able to start in CARP mode

Added by Georgiy Tyutyunnik 12 months ago. Updated 22 days ago.

Status:

Feedback

Priority:

Normal

Assignee:

Marcos M

Category:

pfBlockerNG

Target version:

pfSense - 2.9.0

Start date:

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

25.11

Affected Version:

Affected Plus Version:

Affected Architecture:

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

Download all files

pfbsyslogs.txt (655 Bytes) pfbsyslogs.txt		Georgiy Tyutyunnik, 12/09/2024 04:46 PM
5962813529692161581.jpg (99.7 KB) 5962813529692161581.jpg		Georgiy Tyutyunnik, 12/09/2024 04:46 PM
clipboard-202412091049-6h9fd.png (4.09 KB) clipboard-202412091049-6h9fd.png		dylan mendez, 12/09/2024 04:49 PM

Actions

Copy link

Updated by dylan mendez 12 months ago

File clipboard-202412091049-6h9fd.png clipboard-202412091049-6h9fd.png added

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.

Actions

Copy link