HA Sync not working config version mismatch
-
Hello
We have to firewalls in HA pair both on 2.5.2, config sync is not working because primary reports config version as 21.8 and secondary as 21.7.
Is there any way to fix this?#From forced config sync
Building high availability sync information The other member is on a different configuration version of pfSense. Sync will not be done to prevent problems!Primary logs.
/rc.filter_synchronize: Beginning XMLRPC sync data to https://10.1.1.3:443/xmlrpc.php. /rc.filter_synchronize: XMLRPC versioncheck: 21.7 -- 21.8 /rc.filter_synchronize: The other member is on a different configuration version of pfSense. Sync will not be done to prevent problems! /rc.filter_synchronize: XMLRPC reload data success with https://10.1.1.3:443/xmlrpc.php (pfsense.host_firmware_version). /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.1.1.3:443/xmlrpc.php. /rc.filter_synchronize: XMLRPC reload data success with https://10.1.1.3:443/xmlrpc.php (pfsense.host_firmware_version). /rc.filter_synchronize: XMLRPC versioncheck: 21.7 -- 21.8 /rc.filter_synchronize: The other member is on a different configuration version of pfSense. Sync will not be done to prevent problems! -
One way to fix this is to download config backup, change version from 21.7 to 21.8 in config backup then restore from this file. One think I'm still not sure about is where 21.08 came from in the first place. 2.5.2 should have config Rev 21.7
https://docs.netgate.com/pfsense/en/latest/releases/versions.html#id8
-
I am having the same problem.
As my primary HA member is the one on 21.7 and the secondary is on 21.8, I tried to download the configuration xml and change from 21.8 to 21.7 and then restore the configuration. This didn't work.
I can try and switch the primary from 21.7 to 21.8 (after setting it to backup with carp) but will have to do it outside operating hours, as it scares me pretty good.
Does anyone else have any feedback on what might be causing this? This seems a pretty significant issue that 21.8 isn't even an acknowledged version and my primary system has no knowledge of there being an update.