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

    Continuous replication fails every time

    Scheduled Pinned Locked Moved Xen Orchestra
    31 Posts 8 Posters 7.4k Views 5 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.
    • LPJonL Offline
      LPJon @olivierlambert
      last edited by

      @olivierlambert I have looked into that with no success. I'm not sure if you just change that variable to false or if you just comment it out completely. I have tried both but neither had an affect on my situation. It seems the guessVhdsize variable is related to working with an nfs share for the remote which I don't have.

      More or less you saying that this could be a bug in the master branch of XOCE but that XO is not showing this issue? What branch could I switch to that might be more stable?

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

        1. No, guessVhdSize is NOT related to the remote, but to the way we send data to the destination server. Double check you enabled it correctly and restart XO after the modification.
        2. No, I'm not saying this. Also, there's no stable branch on the sources, if you want something tested and stable, it's XOA 🙂
        LPJonL 1 Reply Last reply Reply Quote 0
        • LPJonL Offline
          LPJon @olivierlambert
          last edited by LPJon

          @olivierlambert It came enabled by default with the upgrade to 5.51.1. What I might be having issues with is how to disable it the proper way for testing. I don't see anywhere where is says how to disable it, only how to enable it since there were failures happening with it disabled...lol. That's a tongue twister, anyway do you have any suggestions or might this be a question for Julien?

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

            I have no idea, guessVhdSize is only an intuition on my side. I'm pinging @julien-f who will try to answer Monday 🙂

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

              @LPJon Like all settings from config.toml and sample.config.toml, you can override it in your user config (probably /etc/xo-server/config.toml?):

              guessVhdSizeOnImport = false
              LPJonL 1 Reply Last reply Reply Quote 0
              • LPJonL Offline
                LPJon @julien-f
                last edited by

                @julien-f Ok....thanks Olivier and Julien. Changing that setting in that way had no effect on the issue. You have any idea what would cause this from one version to the other. XCP-ng is version 7.5 with a second local storage repository.

                1 Reply Last reply Reply Quote 0
                • rizaemet 0R Offline
                  rizaemet 0
                  last edited by

                  Hello,
                  I experience this problem with CR job. xo-server 5.51.1
                  I revent xo-server 5.50.1. No problem with this version.

                  I found these errors in xensource.log. maybe not related:

                  Importing raw VDI R:55902cfbe5b0|vhd_tool_wrapper] vhd-tool failed, returning VDI_IO_ERROR
vhd-tool output: vhd-tool: Non-zero size required (either a pre-existing destination file or specified via --destination-size on the command line)

                  and this:

                  xapi: [error|XenServer-08|12899 INET :::80|Importing raw VDI R:55902cfbe5b0|import] Caught exception: VDI_IO_ERROR: [ Device I/O errors ]
xapi: [debug|XenServer-08|12899 INET :::80|Importing raw VDI R:55902cfbe5b0|taskhelper] the status of R:55902cfbe5b0 is failure; cannot set it to `failure
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] Importing raw VDI R:55902cfbe5b0 failed with exception Server_error(VDI_IO_ERROR, [ Device I/O errors ])
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] Raised Server_error(VDI_IO_ERROR, [ Device I/O errors ])
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 1/12 xapi @ XenServer-08 Raised at file ocaml/xapi/vhd_tool_wrapper.ml, line 59
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 2/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 3/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 4/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 5/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 6/12 xapi @ XenServer-08 Called from file ocaml/xapi/import_raw_vdi.ml, line 81
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 7/12 xapi @ XenServer-08 Called from file ocaml/xapi/import_raw_vdi.ml, line 105
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 8/12 xapi @ XenServer-08 Called from file ocaml/xapi/server_helpers.ml, line 80
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 9/12 xapi @ XenServer-08 Called from file ocaml/xapi/server_helpers.ml, line 99
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 10/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 11/12 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 35
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace] 12/12 xapi @ XenServer-08 Called from file lib/backtrace.ml, line 177
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|backtrace]
xapi: [debug|XenServer-08|13023 UNIX /var/lib/xcp/xapi||dummytaskhelper] task dispatch:session.logout D:8800126a89c1 created by task D:8f42c874d788
xapi: [ info|XenServer-08|13023 UNIX /var/lib/xcp/xapi|session.logout D:04108f92fdfe|xapi] Session.destroy trackid=4319d4a602955613971f7a77e5c9e8cf
xapi: [debug|XenServer-08|640 |xapi events D:0b0842fbd22a|xenops] Event on VM 20192c0a-8918-4e11-8e80-1ac10ff145d1; resident_here = true
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:8f42c874d788|import] Caught exception in import handler: VDI_IO_ERROR: [ Device I/O errors ]
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] VDI.import D:8f42c874d788 failed with exception Unix.Unix_error(Unix.EPIPE, "single_write", "")
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] Raised Unix.Unix_error(Unix.EPIPE, "single_write", "")
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 1/9 xapi @ XenServer-08 Raised at file unix.ml, line 326
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 2/9 xapi @ XenServer-08 Called from file lib/xapi-stdext-unix/unixext.ml, line 463
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 3/9 xapi @ XenServer-08 Called from file lib/xapi-stdext-unix/unixext.ml, line 465
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 4/9 xapi @ XenServer-08 Called from file ocaml/xapi/import_raw_vdi.ml, line 141
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 5/9 xapi @ XenServer-08 Called from file ocaml/xapi/server_helpers.ml, line 80
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 6/9 xapi @ XenServer-08 Called from file ocaml/xapi/server_helpers.ml, line 99
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 7/9 xapi @ XenServer-08 Called from file lib/xapi-stdext-pervasives/pervasiveext.ml, line 24
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 8/9 xapi @ XenServer-08 Called from file map.ml, line 135
xapi: [debug|XenServer-08|640 |xapi events D:0b0842fbd22a|dummytaskhelper] task timeboxed_rpc D:647b3dd768d7 created by task D:0b0842fbd22a
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace] 9/9 xapi @ XenServer-08 Called from file sexp_conv.ml, line 148
xapi: [error|XenServer-08|12899 INET :::80|VDI.import D:9903e89b7f74|backtrace]
xapi: [error|XenServer-08|12899 INET :::80||backtrace] VDI.import D:9903e89b7f74 failed with exception Unix.Unix_error(Unix.EPIPE, "single_write", "")
xapi: [error|XenServer-08|12899 INET :::80||backtrace] Raised Unix.Unix_error(Unix.EPIPE, "single_write", "")
xapi: [error|XenServer-08|12899 INET :::80||backtrace] 1/1 xapi @ XenServer-08 Raised at file (Thread 12899 has no backtrace table. Was with_backtraces called?, line 0
xapi: [error|XenServer-08|12899 INET :::80||backtrace]
                  txsastreT 1 Reply Last reply Reply Quote 0
                  • julien-fJ Offline
                    julien-f Vates 🪐 Co-Founder XO Team
                    last edited by

                    Could this be related to this: https://github.com/vatesfr/xen-orchestra/issues/4640?

                    BluejacketScott created this issue in vatesfr/xen-orchestra

                    closed XO From source restore backup fails with VDI_IO_ERROR #4640

                    1 Reply Last reply Reply Quote 0
                    • txsastreT Offline
                      txsastre @rizaemet 0
                      last edited by

                      @rizaemet-0 could you tell me how have you reverted to 5.50.1 ? thanks

                      rizaemet 0R DanpD 2 Replies Last reply Reply Quote 0
                      • rizaemet 0R Offline
                        rizaemet 0 @txsastre
                        last edited by rizaemet 0

                        @txsastre I'm taking snapshot of XO vm before every update. Simple revent it.

                        Because it is from source so I have no support subscription. I recommend this to you.

                        txsastreT 1 Reply Last reply Reply Quote 1
                        • txsastreT Offline
                          txsastre @rizaemet 0
                          last edited by

                          @rizaemet-0 thanks you've got the right. I already doing this, but I didn't know if you uninstalled it and installed a previous version.

                          it was just curiosity. So I'm gonna rollback to a previous snapshot too.

                          Thank you

                          1 Reply Last reply Reply Quote 1
                          • DanpD Offline
                            Danp Pro Support Team @txsastre
                            last edited by

                            @txsastre I outlined the procedure here --

                            https://xcp-ng.org/forum/post/18974

                            txsastreT 1 Reply Last reply Reply Quote 1
                            • txsastreT Offline
                              txsastre @Danp
                              last edited by

                              @Danp thanks ! but I have rolled back to a previous version ( 5.50.1) and now I'm testing the backup again.

                              1 Reply Last reply Reply Quote 0
                              • F Offline
                                Fungusware
                                last edited by Fungusware

                                Can any comment on the fact that all of these issues are caused because 'import_raw_vdi' doesn't support Chunked transfers?

                                This used to be fine casuse the loophole that allowed a massive Content-Length has been closed.

                                (here: xapi-project/vhd-tool@f978789#diff-a1476b2332c40710d3f1791146a29aeaL484 ).

                                Regards.

                                0 jonludlam committed to xapi-project/vhd-tool 
                                XSI-19 locate VHD footer based on file size

I order to locate the footer in a VHD file or stream, the total length
of that file or stream must be known. This commit passes it when it is
known. This depends on a corresponding change in the ocaml-vhd library.

Signed-off-by: Christian Lindig <christian.lindig@citrix.com>
                                1 Reply Last reply Reply Quote 0
                                • R Offline
                                  RKENS
                                  last edited by

                                  I saw this note relating to ZFS: It is not yet possible to import, migrate or export a VDI to/from a ZFS SR

                                  Could that be why my continuous replication is failing? I'm trying to replicate from one ZFS SR to another on a different server.

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

                                    No, since few release, ZFS should support all operations.

                                    1 Reply Last reply Reply Quote 0
                                    • R Offline
                                      RKENS
                                      last edited by

                                      That's too bad. I don't see where anyone really had any solution.

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

                                        Your CR issue might be related to a XO bug on master, not too a XCP-ng issue 😉

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