Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    XMLRPC sync operation timed out

    HA/CARP/VIPs
    2
    6
    914
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      noel.alanguilan
      last edited by

      Hello folks,

      I am setting up an XMLRPC sync according to the online book: https://docs.netgate.com/pfsense/en/latest/book/highavailability/example-redundant-configuration.html

      The 172.16.X.X were followed and the firewall rules for the sync interface was added to both firewalls

      The sync is happening between an XG-7100 as the primary (172.16.1.2) and an SG-8660 as the secondary (172.16.1.3). The two units are directly connected to each other via a crossover cable. On the XG-7100: eth8 with a VLAN tag and members 8, 9t, 10t and on the SG-8860, OPT4.

      I have been getting the following error messages:

      Apr 24 13:18:11 php-fpm 390 /rc.filter_synchronize: The pfSense software configuration version of the other member could not be determined. Skipping synchronization to avoid causing a problem!
      Apr 24 13:18:11 php-fpm 390 /rc.filter_synchronize: XMLRPC versioncheck: -- 18.9
      Apr 24 13:18:11 php-fpm 390 /rc.filter_synchronize: New alert found: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://172.16.1.3:443. Error: Operation timed out
      Apr 24 13:18:11 php-fpm 390 /rc.filter_synchronize: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://172.16.1.3:443. Error: Operation timed out
      Apr 24 13:18:01 php-fpm 390 /rc.filter_synchronize: Beginning XMLRPC sync data to https://172.16.1.3:443/xmlrpc.php.
      Apr 24 13:18:01 php-fpm 390 /rc.filter_synchronize: New alert found: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://172.16.1.3:443. Error: Operation timed out
      Apr 24 13:18:01 php-fpm 390 /rc.filter_synchronize: A communications error occurred while attempting to call XMLRPC method host_firmware_version: Unable to connect to tls://172.16.1.3:443. Error: Operation timed out

      I am not sure what I did wrong. Can anyone help check it?

      1 Reply Last reply Reply Quote 0
      • N
        noel.alanguilan
        last edited by

        As an addendum, both firewalls are running pfsense 2.4.4 Release p2

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          Hardware in an HA pair must match.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • N
            noel.alanguilan
            last edited by

            Hello. Just a clarification. When you wrote "HA pair must match" do you mean they have to be two units have to be the same model?

            Thank you.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              Yes. Particularly the interfaces.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • N
                noel.alanguilan
                last edited by

                Okay. Noted. Thank you.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.