Bug #14328
closedHA XMLRPC Sync between 1100s can cause errors with Virtual IP Sync
0%
Description
All XMLRPC sync options work fine until you choose "Virtual IP" and then the secondary will get the following crash report:
Crash report begins. Anonymous machine information:
arm64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:28:37 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/aarch64/Z3hsU8Fs/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/Free
Crash report details:
PHP Errors:
[29-Apr-2023 17:53:40 America/Los_Angeles] PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/xmlrpc.php:399
Stack trace:
#0 /usr/local/share/pear/XML/RPC2/Server/CallHandler/Instance.php(141): pfsense_xmlrpc_server->restore_config_section(Array, 900)
#1 /usr/local/share/pear/XML/RPC2/Backend/Php/Server.php(135): XML_RPC2_Server_Callhandler_Instance->__call('pfsense.restore...', Array)
#2 /usr/local/share/pear/XML/RPC2/Backend/Php/Server.php(99): XML_RPC2_Backend_Php_Server->getResponse()
#3 /usr/local/www/xmlrpc.php(988): XML_RPC2_Backend_Php_Server->handleCall()
#4 {main}
thrown in /usr/local/www/xmlrpc.php on line 399
No FreeBSD crash data found.
Updated by Kris Phillips over 2 years ago
Setup two 1100s with stock 23.01 and configured them with OPT as the SYNC port. Tested this and was unable to reproduce is in a lab environment, although with the customer's firewall I could. Unclear at this point what is the cause, but continuing to dig.
Updated by Jim Pingle over 2 years ago
- Project changed from pfSense Plus to pfSense
- Category changed from High Availability to High Availability
- Status changed from New to Duplicate
- Affected Plus Version deleted (
23.01)
Duplicate of #14034, already solved and in system patches.