Project

General

Profile

Actions

Bug #12916

open

pfBlockerNG-devel cron job does not trigger xmlrpc sync

Added by Marcos M about 2 years ago. Updated 12 months ago.

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

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

Tested on pfSense 2.6.0 and pfBlockerNG-devel 3.1.0_1
pfBlockerNG-devel option "Enable Sync" with "Sync to host(s) defined below" selected.
Verified by checking secondary settings after each step.

When the cron job runs (either scheduled or from selecting it under the Update page), it does not trigger an XMLRPC Sync for the package configuration. Manually reloading all does work; see attached cron/reload logs.


Files

cron.txt (5.6 KB) cron.txt scheduled cron job Marcos M, 03/07/2022 01:29 PM
reload.txt (9.22 KB) reload.txt manual reload all Marcos M, 03/07/2022 01:29 PM

Related issues

Related to Regression #14189: pfBlocker-NG: HA-Sync is not workingNew

Actions
Has duplicate Bug #13989: XML-RPC Sync not triggeredDuplicate

Actions
Actions #1

Updated by Israel Goldstein almost 2 years ago

Marcos Mendoza wrote:

Tested on pfSense 2.6.0 and pfBlockerNG-devel 3.1.0_1
pfBlockerNG-devel option "Enable Sync" with "Sync to host(s) defined below" selected.
Verified by checking secondary settings after each step.

When the cron job runs (either scheduled or from selecting it under the Update page), it does not trigger an XMLRPC Sync for the package configuration. Manually reloading all does work; see attached cron/reload logs.

the same issue exists with pfBlockerNG-devel 3.1.0_2

Actions #2

Updated by Alexander Lindqvist almost 2 years ago

I can confirm this issue also on a HA pair running 22.01. We have had this issue since switching to pfBlockerNG-devel a few month ago.

We unchecked "keep settings" and removed 3.1.0_1 today on the backup firewall to troubleshoot this and reinstalled 3.1.0_4 but it didn't sync until we did a reload on the primary firewall.

Actions #3

Updated by Viktor Gurov almost 2 years ago

  • Assignee set to Viktor Gurov
Actions #4

Updated by Caleb Hornbeck over 1 year ago

Viktor Gurov wrote in #note-3:

fix:
https://github.com/pfsense/FreeBSD-ports/pull/1158

I've manually added this fix to a pair of Netgate 7100 running pfSense+ 22.05-RELEASE, and it didn't seem to fix the issue for me; I still had to run a "Reload" task on the primary firewall before the secondary received the updates.

Actions #5

Updated by Marcos M about 1 year ago

  • Has duplicate Bug #13989: XML-RPC Sync not triggered added
Actions #6

Updated by Marcos M 12 months ago

Actions #7

Updated by Marcos M 12 months ago

Actions #8

Updated by Marcos M 12 months ago

Actions #9

Updated by name name 12 months ago

Hello Marcos,

sadly this is not the same bug, because for me on pfSense+ 23.01 no update option worked, not even "Reload".

This means for me currently, there is no workaround. In consequence the firewall on the secondary pfSense+ installation does not have the necessary pfBlockerNG tables loaded, meaning the firewall throws errors - continuously. Also the added protection given by these pfBlockernG tables is not present whenever the backup firewall is active, which is a serious problem.

Please look into it again.

Actions

Also available in: Atom PDF