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

    VDI_IO_ERROR Continuous Replication on clean install.

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    66 Posts 7 Posters 25.0k Views 8 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.
    • arsenieciprianA Offline
      arsenieciprian
      last edited by

      i tryed eveything
      1 downgrade orchestra nodejs to v16 - same
      2 reinstaled xcp-ng clean - same
      Screenshot 2023-02-15 at 08.47.25.png

      1 Reply Last reply Reply Quote 0
      • EddieCh08666741E Offline
        EddieCh08666741
        last edited by

        I've been testing with many variations all clean install from XO from sources all stopped at 5mins. installed 3-4 fresh copy. The only one which work consistently is the node 16 xoa stable version.

        arsenieciprianA 1 Reply Last reply Reply Quote 0
        • arsenieciprianA Offline
          arsenieciprian @EddieCh08666741
          last edited by

          @EddieCh08666741
          what branch in git ?

          EddieCh08666741E 1 Reply Last reply Reply Quote 0
          • EddieCh08666741E Offline
            EddieCh08666741 @arsenieciprian
            last edited by

            @arsenieciprian the official supported XOA.

            1 Reply Last reply Reply Quote 0
            • BrunoMoraisB Offline
              BrunoMorais
              last edited by BrunoMorais

              Hello,
              I'm having the same issue in Delta Backups.
              Opened here a topic here https://xcp-ng.org/forum/topic/7007/a-socket-was-not-created-for-http-request-before-300000ms

              Y 1 Reply Last reply Reply Quote 0
              • Y Offline
                yomono @BrunoMorais
                last edited by

                @BrunoMorais I had the same error yesterday, I rolled back to a previous commit and it started working again. I don't know the exact commit right now, sorry
                (Note that this is not the same error as "vdi_io_error" and the cause it's probably also not the same)

                1 Reply Last reply Reply Quote 0
                • olivierlambertO Offline
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  Are you sure you are on the latest commit on master and did a rebuild?

                  EddieCh08666741E 1 Reply Last reply Reply Quote 0
                  • olivierlambertO Offline
                    olivierlambert Vates 🪐 Co-Founder CEO
                    last edited by

                    We'll be happy to know if you can have the exact commit causing the issue, this will tremendously help 🙂

                    1 Reply Last reply Reply Quote 0
                    • EddieCh08666741E Offline
                      EddieCh08666741 @olivierlambert
                      last edited by

                      @olivierlambert

                      I did another test on fresh new copy of debian 11. Install XOCE. And run some backup to test.

                      M packages/xo-server/config.toml
                      Your branch is up to date with 'origin/master'.

                      e979b3e0-447b-4b02-8448-482316276af4-image.png

                      1 Reply Last reply Reply Quote 0
                      • olivierlambertO Offline
                        olivierlambert Vates 🪐 Co-Founder CEO
                        last edited by

                        @EddieCh08666741 we still have issues to reproduce the issue sadly. So we count on affected users to point to the commit where it started to fail 🙂

                        EddieCh08666741E 1 Reply Last reply Reply Quote 0
                        • EddieCh08666741E Offline
                          EddieCh08666741 @olivierlambert
                          last edited by

                          @olivierlambert i'm doing the git bisect . Will update the commit which cause this issue from restore backup and CR issue.

                          1 Reply Last reply Reply Quote 1
                          • Tristis OrisT Offline
                            Tristis Oris Top contributor
                            last edited by

                            a bit of necroposting.
                            Issue was fixed for me, not sure when. But now CR working with that storage, same config.

                            1 Reply Last reply Reply Quote 1
                            • olivierlambertO olivierlambert marked this topic as a question on
                            • olivierlambertO olivierlambert has marked this topic as solved on
                            • olivierlambertO Offline
                              olivierlambert Vates 🪐 Co-Founder CEO
                              last edited by

                              Good to know it works now 🙂 Thanks for the feedback!

                              1 Reply Last reply Reply Quote 0

                              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                              With your input, this post could be even better 💗

                              Register Login
                              • First post
                                Last post