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

    Has anyone tested 1.21 with a carp cluster?

    Scheduled Pinned Locked Moved 1.2.1-RC Snapshot Feedback and Problems-RETIRED
    34 Posts 7 Posters 13.5k 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.
    • E
      eri--
      last edited by

      Please retry with a recent snapshot and see if the problem goes away.

      1 Reply Last reply Reply Quote 0
      • U
        UnderCover
        last edited by

        im on image

        1.2.1-RC1
        built on Mon Aug 25 07:40:58 EDT 2008

        and get this error with carp

        php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin https://10.1.0.2:443.

        1 Reply Last reply Reply Quote 0
        • A
          ask
          last edited by

          Sync doesn't work across https.

          See http://forum.pfsense.org/index.php/topic,11019.0.html

          1 Reply Last reply Reply Quote 0
          • U
            UnderCover
            last edited by

            ok i went over to http and got this

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

            1 Reply Last reply Reply Quote 0
            • H
              heiko
              last edited by

              Carp works with https in 1.2 as it should, 1.21 have a few bugs, at the moment with ipsec and carp clustering, wait and see…

              regards
              heiko

              1 Reply Last reply Reply Quote 0
              • A
                ask
                last edited by

                "UnderCover",

                Start a shell (via console or ssh) and try

                fetch http://10.1.0.2:80/

                If that doesn't work (with the username and password of the system that's trying to sync – remember, they have to be the same on both boxes), then figure out to fix that first.

                • ask
                1 Reply Last reply Reply Quote 0
                • U
                  UnderCover
                  last edited by

                  will do  thank you  let me know when you need more snapshot carp tests

                  thanks for your help

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

                    Juste a feedback to say that my 1.21 cluster is still running fine without any issue regarding CARP and/or synchronization.

                    ;D

                    1 Reply Last reply Reply Quote 0
                    • A
                      ask
                      last edited by

                      @Juve:

                      Juste a feedback to say that my 1.21 cluster is still running fine without any issue regarding CARP and/or synchronization.

                      Do you use HTTP or HTTPS for the web interface?

                      • ask
                      1 Reply Last reply Reply Quote 0
                      • D
                        databeestje
                        last edited by

                        We confirmed that https synchronisation atleast is not succeeding.

                        It should be fixed in a upcoming snapshot.

                        The carp cluster should otherwise function normally. It does so in my production setup at work.
                        We are still investigating a few other issues here.

                        1 Reply Last reply Reply Quote 0
                        • A
                          ask
                          last edited by

                          @databeestje:

                          We confirmed that https synchronisation atleast is not succeeding.

                          It should be fixed in a upcoming snapshot.

                          Great – will you post a note here when the fix is in a snapshot?

                          @databeestje:

                          The carp cluster should otherwise function normally. It does so in my production setup at work.
                          We are still investigating a few other issues here.

                          I can confirm that CARP (and syncing over http) is working.

                          1 Reply Last reply Reply Quote 0
                          • U
                            UnderCover
                            last edited by

                            can't wait  ;D

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

                              Right, we use HTTP since the snapshot we use has problem with HTTPS.  ;)

                              1 Reply Last reply Reply Quote 0
                              • D
                                databeestje
                                last edited by

                                Carp syncing works normally again.

                                Please confirm

                                1 Reply Last reply Reply Quote 0
                                • U
                                  UnderCover
                                  last edited by

                                  updated to:

                                  1.2.1-RC1
                                  built on Fri Sep 5 13:18:42 EDT 2008

                                  and it still fails

                                  php: : A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    databeestje
                                    last edited by

                                    Doublecheck usernames and check that you have a firewall rule allowing access to the remote webui

                                    1 Reply Last reply Reply Quote 0
                                    • U
                                      UnderCover
                                      last edited by

                                      i have all that and it still fails

                                      1 Reply Last reply Reply Quote 0
                                      • U
                                        UnderCover
                                        last edited by

                                        still failing with http

                                        1.2.1-RC1
                                        built on Wed Sep 10 12:46:21 EDT 2008

                                        with error

                                        Sep 10 16:26:47 php: : New alert found: A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.
                                        Sep 10 16:26:47 php: : A communications error occured while attempting XMLRPC sync with username admin http://10.1.0.2:80.

                                        1 Reply Last reply Reply Quote 0
                                        • D
                                          databeestje
                                          last edited by

                                          I can't replicate it, sorry

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