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

    Backup failed with message "HTTP request has been canceled"

    Scheduled Pinned Locked Moved Xen Orchestra
    17 Posts 3 Posters 1.3k Views 1 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.
    • olivierlambertO Offline
      olivierlambert Vates 🪐 Co-Founder CEO
      last edited by

      Hmm weird, pinging @julien-f

      Maybe too many requests on a XAPI?

      julien-fJ 1 Reply Last reply Reply Quote 0
      • julien-fJ Offline
        julien-f Vates 🪐 Co-Founder XO Team @olivierlambert
        last edited by

        The message HTTP request has been canceled is not correct, it should say HTTP connection abruptly closed, it's an minor error which will be fixed soon.

        It might indeed be triggered by too many connections from XO to the host, in that case, please make sure your XO is up-to-date with this commit: https://github.com/vatesfr/xen-orchestra/commit/51f013851d6d72275a16d37cd92b0ff88e7046d8

        0 julien-f committed to vatesfr/xen-orchestra
        feat(xen-api): limit concurrent calls to 20
        
        Fixes xoa-support#3767
        
        Can be changed via `callConcurrency` option.
        E 1 Reply Last reply Reply Quote 0
        • E Offline
          erwand @julien-f
          last edited by

          @julien-f

          thanks for your reply, where i can find the parameter "callconcurrency" you talk about in your post ?

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

            It will default to 20 if you don't set it up 🙂 That should be enough to make initial tests

            E 1 Reply Last reply Reply Quote 1
            • E Offline
              erwand @olivierlambert
              last edited by

              @olivierlambert I've update to latest XOA and same thing happen today ? Anything i can check to solve ?

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

                Can you be more specific? Are you using XOA or XO from the sources?

                E 1 Reply Last reply Reply Quote 0
                • E Offline
                  erwand @olivierlambert
                  last edited by

                  @olivierlambert Im using XO installed using the script provide by
                  f3fa7d75-1328-4d23-95c5-ad121eb69f19-image.png

                  40e5fbbf-1320-4839-a547-faa3e727e8ad-image.png

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

                    Please check you are on latest master commit. 3rd party scripts are not supported, but just tell us on which commit are you are also double check everything was rebuilt correctly.

                    E 1 Reply Last reply Reply Quote 0
                    • E Offline
                      erwand @olivierlambert
                      last edited by

                      @olivierlambert
                      I've double check and i'm on the laster master check out on 15/06/2021 and everything rebuild

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

                        Can you tell us which commit are you exactly? (just to be sure).

                        We might want to test lower values then.

                        E 1 Reply Last reply Reply Quote 0
                        • E Offline
                          erwand @olivierlambert
                          last edited by

                          @olivierlambert I think: xen-orchestra-202106151431

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

                            The commit id please 🙂 56e4847b6bb85da8ae2dc09e8e9fb7a0db36070a

                            You can have it by doing git rev-parse HEAD

                            E 1 Reply Last reply Reply Quote 0
                            • E Offline
                              erwand @olivierlambert
                              last edited by

                              @olivierlambert said in Backup failed with message "HTTP request has been canceled":

                              git rev-parse HEAD

                              51f013851d6d72275a16d37cd92b0ff88e7046d8

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

                                @erwand said in Backup failed with message "HTTP request has been canceled":

                                51f013851d6d72275a16d37cd92b0ff88e7046d8

                                pinging @julien-f

                                1 Reply Last reply Reply Quote 0
                                • julien-fJ Offline
                                  julien-f Vates 🪐 Co-Founder XO Team @erwand
                                  last edited by

                                  @erwand I don't know how this script works and if the libraries are installed from the repo itself or are coming from npmjs.org, because this change in xen-api has not been published.

                                  You can check by doing something like this:

                                  > cd packages/xo-server
                                  > node -p 'require.resolve("xen-api")'
                                  <root dir>/xen-orchestra/packages/xen-api/dist/index.js
                                  

                                  Also, this error simply indicates that the connection was interrupted between XO and the host during the export of the VDI, this does not necessarily indicate an XO bug, please check your host's logs.

                                  E 1 Reply Last reply Reply Quote 0
                                  • E Offline
                                    erwand @julien-f
                                    last edited by

                                    @julien-f said in Backup failed with message "HTTP request has been canceled":

                                    node -p 'require.resolve("xen-api")'

                                    Hi all,

                                    I think the problem is fixed now. thanks for your help

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