XMLRPC Sync fails after upgrade from 2.3.4 to 2.4.0

aeleus

I have two vm's running pfSense. They were both running 2.3.4 and Config Sync without issues. I upgraded the target machine to 2.4.0, then, after a while, the source machine.

Now, the source machine generates the following error when it tries to sync its configuration:

Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC

Any thoughts?

jimp

So you see that on the primary? Where?

Any other logs in the main system log? Any log entries on the secondary?

aeleus

I get notices on the dashboard page of the configuration source server.

Here's what I get in the System Log, General of the source server:

Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: New alert found: Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.0.0.2:443/xmlrpc.php.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: New alert found: Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: Exception calling XMLRPC method restore_config_section # Impossible to encode value '' from type 'NULL'. No analogous type in XML_RPC.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.0.0.2:443/xmlrpc.php.
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: XMLRPC versioncheck:17.0 – 17.0
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: XMLRPC reload data success with https://10.0.0.2:443/xmlrpc.php (pfsense.host_firmware_version).
Oct 15 02:05:25 php-fpm 41325 /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.0.0.2:443/xmlrpc.php.
Oct 15 02:05:24 check_reload_status Syncing firewall

I don't see any corresponding errors on the target machine.

PiBa

Can you try disabling some of the sync checkboxes to try and find out if maybe 1 particular section of the configuration is causing a problem?

jimp

Also: Do you have any packages installed with sync enabled?

I have no trouble with XMLRPC sync on 2.4 on two different clusters.

aeleus

@PiBa:

Can you try disabling some of the sync checkboxes to try and find out if maybe 1 particular section of the configuration is causing a problem?

Unchecking the option to sync Virtual IPs revealed the problem. I don't have any VIP's configured in this setup. I guess 2.3.4 just ignored that and synced everything else.

Seems like a bug with 2.4.0 though. VIP's should just be ignored if none are configured.

Thanks for the help!

jimp

I was able to reproduce it by trying to delete the last VIP, so it is definitely a problem syncing empty sections, at least VIPs.

https://redmine.pfsense.org/issues/7953

We'll work on it, thanks!

pdrass

I just found this thread. I have this same problem!

https://forum.pfsense.org/index.php?topic=140014.0

I can't find much about this or how to fix the error. It's either because it doesn't like a self signed cert, maybe it doesn't like httpS on an alternative port of 10000 or something else.

I did notice I had to put the credentials in this format on the last version "admin" for the user instead of "root". I haven't tried root…

Any insight? Not much is logged other than it failed in the pfblockerng.log file in /var/log/pfblocker/