Project

General

Profile

Actions

Bug #15916

open

pfBlockerNG dnsbl daemon not able to start in CARP mode

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

Status:
New
Priority:
Normal
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
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

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 #1

Updated by dylan mendez 12 days 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.

Actions

Also available in: Atom PDF