pfSense English Support > CARP/VIPs

High Avail. Sync broken

(1/4) > >>

vigorfac:
Hello everyone.

I have two pfsenses so far in 2.3.
It has an interface with a lan and a sync.
I made the update in 2.4
Since the sync does not work anymore and I can not find the explanation.
Maybe you can help me.
Thank you very much.

Here are the pfsense master logs when he tries to sync.


   01/10/1930 17:45   check_reload_status      Syncing firewall
   01/10/1930 17:45   php-fpm   53724   /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.88.88.2:443/xmlrpc.php.
   01/10/1930 17:45   php-fpm   53724   /rc.filter_synchronize: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://10.88.88.2:443. Error: Operation timed out
   01/10/1930 17:45   php-fpm   53724   /rc.filter_synchronize: New alert found: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://10.88.88.2:443. Error: Operation timed out
   01/10/1930 17:45   php-fpm   53724   /rc.filter_synchronize: Beginning XMLRPC sync data to https://10.88.88.2:443/xmlrpc.php.
   01/10/1930 17:46   php-fpm   53724   /rc.filter_synchronize: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://10.88.88.2:443. Error: Operation timed out
   01/10/1930 17:46   php-fpm   53724   /rc.filter_synchronize: New alert found: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://10.88.88.2:443. Error: Operation timed out
   01/10/1930 17:46   php-fpm   53724   /rc.filter_synchronize: XMLRPC versioncheck: -- 17.3
   01/10/1930 17:46   php-fpm   53724   /rc.filter_synchronize: The pfSense software configuration version of the other member could not be determined. Skipping synchronization to avoid causing a problem!

0 log on the Pfsense Slave.

andipandi:
Same as mine? https://forum.pfsense.org/index.php?topic=139032.0

Once primary IP gets blocked, I get the timeouts too. So might be the same. No solution on that though..

dotdash:
Commented on the other thread, but you need to have both boxes on the same version- upgrade them both.

vigorfac:
Both Pfsense are on

2.4.1-RELEASE (amd64)
built on Sun Oct 22 17:26:33 CDT 2017
FreeBSD 11.1-RELEASE-p2

vigorfac:
@andipadi
I don't think it was the same issue, i have 0 log on secondary pfsense.

This morning I try to install from scratch on the two pfsense with 2.4.1-release version, same issue !

Navigation

[0] Message Index

[#] Next page

Go to full version