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

    Sync Communication error occurred

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    9 Posts 2 Posters 1.1k Views
    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.
    • S
      sshami
      last edited by

      am newbie in Pfsense and setup pfsense as software in cluster with two VMs. Carp is working fine even i can see one as a master node and secondary as Backup if i restart first node second node become master so far high availability looks good.

      Setup details:
      1 WAN interface
      1 Sync interface (Synchronize Interface)
      1 Virtual IP for carp
      Configured: SystemHigh Availability Sync

      On the master node i am getting following error Notices :
      Communications error occurred
      A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-25 00:03:09
      A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-25 00:03:10

      Other question is how to verify my sync is working properly, i thought to create one user on master node but its not automatically sync new user to backup node even firewall rules.

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @sshami
        last edited by

        @sshami said in Sync Communication error occurred:

        On the master node i am getting following error Notices :
        Communications error occurred
        A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-25 00:03:09
        A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-25 00:03:10

        So the sync is not working. Check the system log for details.

        Ensure that the secondary allow access on the sync interfaces and that the password for the sync user is the same on both boxes.

        Other question is how to verify my sync is working properly, i thought to create one user on master node but its not automatically sync new user to backup node even firewall rules.

        When you get no errors when applying a configuration change, the sync worked. 🙂
        Also in the system log you can see an entry for each sync attempt.

        S 1 Reply Last reply Reply Quote 1
        • S
          sshami @viragomann
          last edited by

          This post is deleted!
          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @sshami
            last edited by

            @sshami
            So the communication on the sync network seems to be blocked somehow.

            Is the sync network mask config on the secondary correct?

            Possibly it is blocked by the hypervisor due to a missing configuration detail.

            S 2 Replies Last reply Reply Quote 0
            • S
              sshami @viragomann
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • S
                sshami @viragomann
                last edited by

                @viragomann
                Even following error getting without syncing secondary node, only having master also without sync same error.

                A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-27 11:21:31
                A communications error occurred while attempting to call XMLRPC method host_firmware_version: @ 2021-04-27 11:21:32

                Both have same version : 2.5.1-RELEASE (amd64).
                Is host_firmware_version different ?

                1 Reply Last reply Reply Quote 0
                • V
                  viragomann
                  last edited by

                  @sshami
                  Yes, the error message suggests that there might be different versions installed, but as the ping to the secondary shows, you can't access it from the master at all.

                  You can sniff the traffic to see where the packets go, maybe on Proxmox and on pfSense.

                  Check if there is something in the secondarys system log indicating a network configuration failure.

                  Ensure that 'hardware checksum offloading' is disabled on both, master and secondary.

                  Do you run packages like Snort or Suricata?

                  Ensure that the Admin-webGUI listens on the same port and that HTTPS is enabled on both.
                  BTW: port 443 is not a really good choice. Better to use an unusual port.

                  S 2 Replies Last reply Reply Quote 0
                  • S
                    sshami @viragomann
                    last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • S
                      sshami @viragomann
                      last edited by

                      @viragomann Thanks for your input!
                      Issue solved!
                      It was issue basically frame untagged on switch of particular VLAN, so after tagging it works and able to connect secondary and sync!

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