pfSense

I cannot replicate the problem as stated and nothing changed between the previous builds which would have impacted XMLRPC that I can tell.

This site is not for support or diagnostic discussion, please post on the Netgate Forum in the category for 2.5.2 snapshots at https://forum.netgate.com/category/85/2-5-2-development-snapshots and describe your problem in more detail. Please provide additional log entries from around when the error occurs and what it takes to trigger the error.

Also make sure both nodes are on the same build. If an error happens when they are on mismatched builds, that's not a valid report as it's not a supported HA state.

At first I couldn't reproduce it, but now I can every time. Not sure what changed. It didn't show up in the logs or notices initially, but after I restarted php (16/11 from the console) it was logged.

I noticed that the error message was incomplete. I managed to fix that up but it isn't terribly helpful:

Jun 16 10:49:20     php-fpm     66863     /rc.filter_synchronize: New alert found: A communications error occurred while attempting to call XMLRPC method restore_config_section: Error writing request 

I checked out the request body and it is the whole config sync, though I checked and the configuration is syncing.

On the target system, the XMLRPC lock file in /tmp/xmlrpc.lock is left, so something on the secondary node must be bailing before it finishes the sync process.

There is nothing in the logs on the secondary, however, to indicate a problem.

After checking many, many different things (SSL, crypto settings, nginx settings, and more) I went back and tried older snapshots:

• 20210604-1008 OK
• 20210609-0300 OK
• 20210610-1655 Fail
• 20210615-1851 Fail

Between 20210609-0300 and 20210610-1655 the most significant change is a ports update which updated PHP from 7.4.19 to 7.4.20.

pear-HTTP_Request2 downgraded to 2.3.0,1

Latest 2.5.2 build looks good with pear-HTTP_Request2 2.3.0,1.

Moving this ahead to 2.6.0 for (hopefully) a long term fix.

I've added a patch from upstream [1] to devel/pear-HTTP_Request2, version 2.4.2_1,1

[1] https://github.com/pear/HTTP_Request2/commit/63e6f932ab4004f0c09a080d370861d0323b6d33

Looks good with that version.

On snapshot 2.6.0.a.20210701.0100 with php74-pear-HTTP_Request2-2.4.2_1,1 and it's working every time. Zero failures when testing.

I think we can call this one closed.

Thanks!

Updating subject, but also excluding from release notes since this was never a problem in a release.