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

    Cant figure out why I keep getting this error

    Scheduled Pinned Locked Moved
    HA/CARP/VIPs
    3
    5
    4.3k
    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.
    • J
      jhabers
      last edited by

      New alert found: A communications error occured while attempting XMLRPC sync with username admin http://192.168.51.3:80.

      I get these on my Master PF Sense, 192.168.51.3 is the PFSYNC Interface on my backup PF sense

      Any Idea?

      Thanks, Jon

      Aug 16 20:11:20 kernel: arp: 192.168.50.16 moved from 00:21:9b:a6:f8:de to 00:21:9b:a6:f8:e2 on em0
      Aug 16 20:11:20 kernel: arp: 192.168.50.13 moved from 84:2b:2b:0c:85:bf to 84:2b:2b:0c:85:bb on em0
      Aug 16 20:11:20 kernel: arp: 192.168.50.13 moved from 84:2b:2b:0c:85:b9 to 84:2b:2b:0c:85:bf on em0
      Aug 16 20:11:20 kernel: arp: 192.168.50.13 moved from 84:2b:2b:0c:85:bf to 84:2b:2b:0c:85:b9 on em0
      Aug 16 20:11:13 php: : Beginning XMLRPC sync to http://192.168.51.3:80.
      Aug 16 20:11:13 php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://192.168.51.3:80.
      Aug 16 20:11:13 php: : A communications error occured while attempting XMLRPC sync with username admin http://192.168.51.3:80.
      Aug 16 20:11:10 kernel: arp: 192.168.50.10 moved from 84:2b:2b:1a:94:8c to 84:2b:2b:1a:94:90 on em0
      Aug 16 20:11:10 kernel: arp: 192.168.50.10 moved from 84:2b:2b:1a:94:8e to 84:2b:2b:1a:94:8c on em0
      Aug 16 20:11:10 kernel: arp: 192.168.50.10 moved from 84:2b:2b:1a:94:8c to 84:2b:2b:1a:94:8e on em0
      Aug 16 20:11:10 kernel: arp: 192.168.50.15 moved from 00:21:9b:a6:f8:3a to 00:21:9b:a6:f8:3c on em0
      Aug 16 20:11:10 kernel: arp: 192.168.50.15 moved from 00:21:9b:a6:f8:3c to 00:21:9b:a6:f8:3a on em0
      Aug 16 20:10:24 kernel: arp: 192.168.50.16 moved from 00:21:9b:a6:f8:e2 to 00:21:9b:a6:f8:de on em0
      Aug 16 20:10:16 kernel: arp: 192.168.50.13 moved from 84:2b:2b:0c:85:bb to 84:2b:2b:0c:85:bf on em0
      Aug 16 20:09:58 php: : Beginning XMLRPC sync to http://192.168.51.3:80.
      Aug 16 20:09:56 check_reload_status: reloading filter
      Aug 16 20:09:52 kernel: carp1: link state changed to UP
      Aug 16 20:09:52 kernel: carp1: INIT -> MASTER (preempting)
      Aug 16 20:09:52 kernel: carp1: link state changed to DOWN
      Aug 16 20:09:52 kernel: carp0: link state changed to UP
      Aug 16 20:09:52 kernel: carp0: INIT -> MASTER (preempting)
      Aug 16 20:09:52 kernel: carp0: link state changed to DOWN
      Aug 16 20:09:52 kernel: carp1: link state changed to DOWN

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Those errors mean that multiple devices are using the same IP address - or it looks that way to the OS.

        The most common cause is either two devices fighting over the same IP, or there may be some other misconfigurations that could cause it, such as using proxy ARP VIPs on a CARP cluster instead of CARP or Other type VIPs.

        Or you have something amiss in how you have your NICs/switches plugged in

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • J
          jhabers
          last edited by

          Hmm Im using Broadcoms Smart Load Balancing with 4 NICs teamed on each server. Could that be causing confusion?

          I seemed to got rid of error "alert found: A communications error occured while attempting XMLRPC sync with username admin http://192.168.51.3:80" by creating a rule on the pfsync interface allowing all

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            @jhabers:

            Hmm Im using Broadcoms Smart Load Balancing with 4 NICs teamed on each server. Could that be causing confusion?

            yeah some load balancing/NIC teaming does that normally. Otherwise it's generally indicative of an IP conflict or ARP poisoning.

            1 Reply Last reply Reply Quote 0
            • J
              jhabers
              last edited by

              @cmb:

              @jhabers:

              Hmm Im using Broadcoms Smart Load Balancing with 4 NICs teamed on each server. Could that be causing confusion?

              yeah some load balancing/NIC teaming does that normally. Otherwise it's generally indicative of an IP conflict or ARP poisoning.

              thanks, is it safe to ignore those messages? anyway to get them not to log?

              1 Reply Last reply Reply Quote 0
              • First post
                Last post