Project

General

Profile

Actions
Copy link

Bug #16591

open

NRPE XMLRPC Error

Added by Tom Edwards 6 days ago. Updated 4 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
-
Category:
NRPE
Target version:
-
Start date:
Due date:
% Done:

0%

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

Description

When running 25.11 in HA. Installing the NRPE package errors get thrown.

PHP ERROR: Type: 1, File: /etc/inc/pfsense-utils.inc, Line: 4480, Message: Uncaught TypeError: call_user_func(): Argument #1 ($callback) must be a valid callback, function "nrpe_plugin_xmlrpc_send" not found or invalid function name in /etc/inc/pfsense-utils.inc:4480
Stack trace:
#0 /etc/rc.filter_synchronize(362): pkg_call_plugins()
#1 {main}
thrown

Files

Download all files
PHP_errors_primary.log (744 Bytes) PHP_errors_primary.log Georgiy Tyutyunnik, 12/17/2025 03:15 PM
PHP_errors_secondary.log (11.1 KB) PHP_errors_secondary.log Georgiy Tyutyunnik, 12/17/2025 03:15 PM
16591.patch (629 Bytes) 16591.patch Christopher Cope, 12/19/2025 12:52 AM
Actions
Copy link
 #1

Updated by Jim Pingle 6 days ago

  • Project changed from pfSense Plus to pfSense Packages
  • Category changed from XMLRPC to NRPE
  • Release Notes deleted (Default)
Actions
Copy link
 #2

Updated by Georgiy Tyutyunnik 6 days ago

confirmed
tested on:
25.11-RELEASE (amd64)
built on Mon Dec 15 17:04:00 UTC 2025
FreeBSD 16.0-CURRENT
crashes from primary and secondary attached

Actions
Copy link
 #3

Updated by Christopher Cope 5 days ago

Also confirmed on

25.11-RELEASE (amd64)
built on Mon Dec 15 12:04:00 EST 2025
FreeBSD 16.0-CURRENT

Patch attached that fixes this behavior. Pending a merge request.

Actions
Copy link
 #4

Updated by Kris Phillips 4 days ago

Customer reported that the patch file breaks XMLRPC sync for firewall rules. I have confirmed this behavior by adding a rule on primary that was disabled and it did not copy over to the secondary, even with a manual force sync.

Actions
Copy link
 #5

Updated by Christopher Cope 4 days ago

To be clear, the patch doesn't break sync. The customer was already having sync issues, one of which was this one. The patch wasn't intended to, nor did it fix his other unrelated issue.

Actions
Copy link

Also available in: Atom PDF