Error Continous Replications 5.18.0



  • ok I removed all of them, only master remained. restarted EVERYTHING.
    tested again, and de continuous replication fails.
    in one specific vm, i can see that exporting is at 100% and importing stops at 42%, then it stops wit error. this time is VDI_IO_ERROR(Device I/O errors)



  • well, may be its a problem on my side, I will keep trying.
    If I find it I will tell you.
    Thanks for your time !



  • @bsastre Have you tried this where both hosts are running the same version of XS?



  • hi @Danp yes, I've done a lot of combinations.

    nevermind, maybe in summer I will try to reinstall everything from scratch and try again.

    thanks again for your time and effort.



  • well tried again.

    but this time with a XS 7.1 instead XCP 7.4

    there are 3 servers
    192.168.222.210
    192.168.222.220
    192.168.222.230

    192.168.222.210 is the master
    192.168.222.220 is the host that holds de VM being CR.

    in XO there is only one server connected at the settings 192.168.222.210 (master)

     [{"message":"VDI_IO_ERROR(Device I/O errors)","stack":"XapiError: VDI_IO_ERROR(Device I/O errors)\n at wrapError (/opt/xen-orchestra/packages/xen-api/src/index.js:111:9)\n at getTaskResult (/opt/xen-orchestra/packages/xen-api/src/index.js:191:26)\n at Xapi._addObject (/opt/xen-orchestra/packages/xen-api/src/index.js:797:23)\n at /opt/xen-orchestra/packages/xen-api/src/index.js:835:13\n at arrayEach (/opt/xen-orchestra/node_modules/lodash/_arrayEach.js:15:9)\n at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10)\n at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:830:12)\n at onSuccess (/opt/xen-orchestra/packages/xen-api/src/index.js:853:11)\n at run (/opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:66:22)\n at /opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:83:30\n at flush (/opt/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9)\n at process._tickCallback (internal/process/next_tick.js:112:11)","code":"VDI_IO_ERROR","params":["Device I/O errors"],"url":"https://192.168.222.230/import_raw_vdi/?format=vhd&vdi=OpaqueRef%3Abedee949-add4-2d80-57b3-b525b17ae751&session_id=OpaqueRef%3Aa855be20-04e6-8b24-04d9-8133b0ec4bde&task_id=OpaqueRef%3A7c1febb8-07f8-e9e6-6b1e-56bdd174a324"}]
    


  • as I've been seen that the problem seems related to 192.168.222.230 (host)
    I tried 2 things.
    1- put all the VM on him (error)
    2-stopped that host... error

     [{"message":"connect EHOSTUNREACH 192.168.222.230:443","stack":"Error: connect EHOSTUNREACH 192.168.222.230:443\n at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1173:14)","errno":"EHOSTUNREACH","code":"EHOSTUNREACH","syscall":"connect","address":"192.168.222.230","port":443,"url":"https://192.168.222.230/export_raw_vdi/?format=vhd&vdi=OpaqueRef%3A31a4a757-7c2a-a54e-78c1-42c154b3aeaf&session_id=OpaqueRef%3A3d4e433b-562c-3a09-55e0-58c20fd78611&task_id=OpaqueRef%3Ad530059f-4a3f-7326-6aa4-33fbf4203e93"}]```


  • still 230 stopped.
    tried to do the same CR but with de VM also stopped.
    another error.
    Job canceled to protect the VDI chain



  • removed 230 from Pool

    now the error is on 220

        [{"message":"VDI_IO_ERROR(Device I/O errors)","stack":"XapiError: VDI_IO_ERROR(Device I/O errors)\n at wrapError (/opt/xen-orchestra/packages/xen-api/src/index.js:111:9)\n at getTaskResult (/opt/xen-orchestra/packages/xen-api/src/index.js:191:26)\n at Xapi._addObject (/opt/xen-orchestra/packages/xen-api/src/index.js:797:23)\n at /opt/xen-orchestra/packages/xen-api/src/index.js:835:13\n at arrayEach (/opt/xen-orchestra/node_modules/lodash/_arrayEach.js:15:9)\n at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10)\n at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:830:12)\n at onSuccess (/opt/xen-orchestra/packages/xen-api/src/index.js:853:11)\n at run (/opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:66:22)\n at /opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:83:30\n at flush (/opt/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9)\n at process._tickCallback (internal/process/next_tick.js:112:11)","code":"VDI_IO_ERROR","params":["Device I/O errors"],"url":"https://192.168.222.220/import_raw_vdi/?format=vhd&vdi=OpaqueRef%3A8c783ae0-1aec-93c6-3f7a-dfcff996eddc&session_id=OpaqueRef%3A3d4e433b-562c-3a09-55e0-58c20fd78611&task_id=OpaqueRef%3Abcec4201-e08d-be22-09f3-6f8b5c7b4a9d"}]
    
    


  • only one server in the pool.
    same error, now pointing to the 210

     [{"message":"VDI_IO_ERROR(Device I/O errors)","stack":"XapiError: VDI_IO_ERROR(Device I/O errors)\n at wrapError (/opt/xen-orchestra/packages/xen-api/src/index.js:111:9)\n at getTaskResult (/opt/xen-orchestra/packages/xen-api/src/index.js:191:26)\n at Xapi._addObject (/opt/xen-orchestra/packages/xen-api/src/index.js:797:23)\n at /opt/xen-orchestra/packages/xen-api/src/index.js:835:13\n at arrayEach (/opt/xen-orchestra/node_modules/lodash/_arrayEach.js:15:9)\n at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10)\n at Xapi._processEvents (/opt/xen-orchestra/packages/xen-api/src/index.js:830:12)\n at onSuccess (/opt/xen-orchestra/packages/xen-api/src/index.js:853:11)\n at run (/opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:66:22)\n at /opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:83:30\n at flush (/opt/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9)\n at process._tickCallback (internal/process/next_tick.js:112:11)","code":"VDI_IO_ERROR","params":["Device I/O errors"],"url":"https://192.168.222.210/import_raw_vdi/?format=vhd&vdi=OpaqueRef%3Ab0bd681d-783e-4ae3-20fb-2be3a37d442e&session_id=OpaqueRef%3A3d4e433b-562c-3a09-55e0-58c20fd78611&task_id=OpaqueRef%3A4b975017-2b56-e68b-2099-ccb59d24dbd3"}]```


  • tried with backup legacy, only 1 host.

    host.listMissingPatches
    {
      "host": "d64f7775-2682-4c46-bb42-ab565fc66f37",
      "id": "d64f7775-2682-4c46-bb42-ab565fc66f37"
    }
    {
      "message": "no such object",
      "stack": "XoError: no such object
        at factory (/opt/xen-orchestra/packages/xo-common/src/api-errors.js:21:31)
        at Xo.getObject (/opt/xen-orchestra/packages/xo-server/src/xo.js:65:25)
        at /opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:121:24
        at /opt/xen-orchestra/node_modules/lodash/_createBaseFor.js:17:11
        at baseForOwn (/opt/xen-orchestra/node_modules/lodash/_baseForOwn.js:13:20)
        at /opt/xen-orchestra/node_modules/lodash/_createBaseEach.js:17:14
        at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10)
        at Xo.resolveParams (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:115:10)
        at /opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:277:49
        at Generator.next (<anonymous>)
        at step (/opt/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:40:221)
        at _next (/opt/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:40:409)
        at run (/opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:66:22)
        at /opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:83:30
        at flush (/opt/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9)
        at process._tickCallback (internal/process/next_tick.js:112:11)",
      "code": 1,
      "data": {
        "id": "d64f7775-2682-4c46-bb42-ab565fc66f37",
        "type": "host"
      }
    } ```


  • trying to copy to another SR. 1 host, same error

    host.listMissingPatches
    {
      "host": "d64f7775-2682-4c46-bb42-ab565fc66f37",
      "id": "d64f7775-2682-4c46-bb42-ab565fc66f37"
    }
    {
      "message": "no such object",
      "stack": "XoError: no such object
        at factory (/opt/xen-orchestra/packages/xo-common/src/api-errors.js:21:31)
        at Xo.getObject (/opt/xen-orchestra/packages/xo-server/src/xo.js:65:25)
        at /opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:121:24
        at /opt/xen-orchestra/node_modules/lodash/_createBaseFor.js:17:11
        at baseForOwn (/opt/xen-orchestra/node_modules/lodash/_baseForOwn.js:13:20)
        at /opt/xen-orchestra/node_modules/lodash/_createBaseEach.js:17:14
        at forEach (/opt/xen-orchestra/node_modules/lodash/forEach.js:38:10)
        at Xo.resolveParams (/opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:115:10)
        at /opt/xen-orchestra/packages/xo-server/src/xo-mixins/api.js:277:49
        at Generator.next (<anonymous>)
        at step (/opt/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:40:221)
        at _next (/opt/xen-orchestra/packages/xo-server/dist/xo-mixins/api.js:40:409)
        at run (/opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:66:22)
        at /opt/xen-orchestra/node_modules/core-js/modules/es6.promise.js:83:30
        at flush (/opt/xen-orchestra/node_modules/core-js/modules/_microtask.js:18:9)
        at process._tickCallback (internal/process/next_tick.js:112:11)",
      "code": 1,
      "data": {
        "id": "d64f7775-2682-4c46-bb42-ab565fc66f37",
        "type": "host"
      }
    } ```


  • @txsastre said in Error Continous Replications 5.18.0:

    Job canceled to protect the VDI chain

    Job canceled to protect the VDI chain is NOT an error. Please read the documentation related to this 😉



  • @olivierlambert said in Error Continous Replications 5.18.0:

    @txsastre said in Error Continous Replications 5.18.0:

    Job canceled to protect the VDI chain

    Job canceled to protect the VDI chain is NOT an error. Please read the documentation related to this 😉

    yes, I know its not an error, you have the right I read about it weeks ago. But, what about all the problems I have with CR ? I don't know what else try. 😞



  • well, another try.
    I've downloaded XOA, also registered it and upgraded to 5.18.3 (same as XO from sources), and it works really smooth !

    I've seen that the appliance is on a debian 8, I installed the sources on a debian 9, maybe is that the problem ?

    I will try tomorrow XO over a debian 8 64.

    cross fingers.



  • That's really why we build and support XOA: to have a consistent experience for production installs… Otherwise it's almost impossible to predict some outcome depending on the platform and what's installed inside.



  • hi @olivierlambert you've got the right.
    otherwise, I tried with : Debian 8, Debian 9, Ubuntu 16:04, created following your instructions, and also done with a script.
    same result everytime.

    when trying a CR the first time is a full backup, ok, when trying a new backup on the same VM, it should be an incremental one, but I receive an error. When I try again, a new full backup is done... no deltas here.

    very strange altogether.



  • I think thats the main problem, still not lucky with finding why.

    Apr 30 19:12:08 ubuntu16 xo-server[1002]: Error: missing base VDI (copy of 8a13a523-ec92-49bc-af4a-00205ea6a610)
    
    

    .



  • Just to help fill in the discussion a bit here is an issue on my GH repo for the CE installer that we're trying to determine where the issue is.

    I tested this last night in my personal lab and had no issues using CR.



  • hi there @DustinB3403 @olivierlambert
    as you know I've been doing a lot of tests in this late weeks, and I haven't found the problem of why was unable to do a correct CR.

    A few hours ago I saw the new release 5.19, upgraded the XOCE and now it works like a charm! 🙂

    Thanks @DustinB3403 for your tests and help in GH
    also thanks to @olivierlambert and team for helping in the forum.
    hope my problem has revealed a bug in XO especially in backup-ng

    I attach a test that I was doing this afternoon I tried a CR every minute, it started really fine, then some "Job canceled to protect the VDI chain" appeared, but all of us know that's not an error, its a protection 😉

    Really appreciate the time you have dedicated to me, thanks a lot.
    We'll see you here !

    0_1525193091878_Selecció_018.jpg


Log in to reply