XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Error: couldn't instantiate any remote

    Scheduled Pinned Locked Moved Xen Orchestra
    33 Posts 8 Posters 4.7k Views 7 Watching
    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.
    • florentF Offline
      florent Vates πŸͺ XO Team
      last edited by

      Hello,

      We could reproduce it with a job with only continuous replication. the PR with the fix is here : https://github.com/vatesfr/xen-orchestra/pull/6437/files

      Can you confirm it fixes the problem ?

      Regards
      Florent

      fbeauchamp opened this pull request in vatesfr/xen-orchestra

      closed fix(xo-server): fix running replication job #6437

      JamfoFLJ screame1S A 3 Replies Last reply Reply Quote 1
      • JamfoFLJ Offline
        JamfoFL @olivierlambert
        last edited by

        @olivierlambert No... only with CR. Delta backups still work like a champ!

        1 Reply Last reply Reply Quote 0
        • JamfoFLJ Offline
          JamfoFL @florent
          last edited by

          @florent Thanks for the update, Florent!

          Unfortunately, my office is in the direct path of Hurricane Ian, so we are going to be closed for the next day or two, and I won't have an opportunity to try the patch until after we return from the storm!

          Hopefully Screame1 (who originally submitted the error) will be able to test and verify, and I will do the same once I am back to the office.

          Thanks again for you post, and I'll be sure to update you as soon as I can!

          screame1S 1 Reply Last reply Reply Quote 0
          • screame1S Offline
            screame1 @florent
            last edited by screame1

            @florent @JamfoFL I'd be happy to try to test. I have changed the source code on my server per the change you made.

            That's where my knowledge turns fuzzy. How do I go about compiling that change and trying to run it?

            Thanks for the quick response on this issue!

            AtaxyaNetworkA 1 Reply Last reply Reply Quote 0
            • screame1S Offline
              screame1 @JamfoFL
              last edited by

              @JamfoFL I've been watching the coverage of Ian from here in Indiana. You and everyone in the path are in my thoughts. Stay safe!

              1 Reply Last reply Reply Quote 0
              • AtaxyaNetworkA Offline
                AtaxyaNetwork Ambassador @screame1
                last edited by

                @screame1 You can do something like this:

                cd your_folder_where_xo_is
                git checkout fix_continuous_replication
                git pull -r
                yarn
                yarn build
                

                (i didn't use XO source since a long time, so maybe i'm wrong ^^)

                screame1S 1 Reply Last reply Reply Quote 2
                • screame1S Offline
                  screame1 @AtaxyaNetwork
                  last edited by

                  @AtaxyaNetwork Thanks! I was able to find instructions in another thread, so I was down the path when you replied. I've applied the patch, restarted the server, and it appears to have started the backup correctly. It will obviously take a few minutes to know if the backups work, but this patch has moved me past the error reported.

                  Thanks again for the efforts @florent @JamfoFL and @AtaxyaNetwork !

                  1 Reply Last reply Reply Quote 1
                  • A Offline
                    alcaraz73 @florent
                    last edited by

                    @florent Thanks, patch applied and CR is working now.

                    JamfoFLJ 1 Reply Last reply Reply Quote 1
                    • JamfoFLJ Offline
                      JamfoFL @alcaraz73
                      last edited by

                      @alcaraz73 @screame1 @AtaxyaNetwork @florent @Danp @olivierlambert I know I'm late back to the party, but just got back into our office after Hurricane Ian. Thanks to all for your well wishes... I was very fortunate to come out with no damage, and was only without power for about 12 hours.

                      Now that I'm back, I also applied the fixes here (and updated to the latest commit) and can confirm continuous replication is working like a champ.

                      Thanks to everyone involved for the help!

                      1 Reply Last reply Reply Quote 2
                      • olivierlambertO Offline
                        olivierlambert Vates πŸͺ Co-Founder CEO
                        last edited by

                        Oh wow, you were lucky indeed!

                        Happy to know you are safe πŸ™‚

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