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

    Cannot take snapshots with XO

    Scheduled Pinned Locked Moved Xen Orchestra
    6 Posts 3 Posters 1.5k 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.
    • G Offline
      guiltykeyboard
      last edited by olivierlambert

      Every time I try to take a snapshot in XO, I get the following message: Unknown error from the peer. When looking at it under settings > Logs, it says:

      MESSAGE_REMOVED()
      
      This is a XenServer/XCP-ng error.
      
      This is the full text of the log:
      
      vm.snapshot
      {
        "id": "ad416996-73f5-1b47-4bd3-c4a96e913b7a"
      }
      {
        "code": "MESSAGE_REMOVED",
        "params": [],
        "call": {
          "method": "Async.VM.snapshot_with_quiesce",
          "params": [
            "OpaqueRef:bb24b322-2517-4f8c-8f3a-640d4f38c29b",
            "host.domain.com_2020-10-22T01:35:26.549Z"
          ]
        },
        "message": "MESSAGE_REMOVED()",
        "name": "XapiError",
        "stack": "XapiError: MESSAGE_REMOVED()
          at Function.wrap (/etc/xo/xo-builds/xen-orchestra-202002022028/packages/xen-api/src/_XapiError.js:16:11)
          at /etc/xo/xo-builds/xen-orchestra-202002022028/packages/xen-api/src/index.js:630:55
          at Generator.throw (<anonymous>)
          at asyncGeneratorStep (/etc/xo/xo-builds/xen-orchestra-202002022028/packages/xen-api/dist/index.js:58:103)
          at _throw (/etc/xo/xo-builds/xen-orchestra-202002022028/packages/xen-api/dist/index.js:60:291)
          at tryCatcher (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/util.js:16:23)
          at Promise._settlePromiseFromHandler (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/promise.js:547:31)
          at Promise._settlePromise (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/promise.js:604:18)
          at Promise._settlePromise0 (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/promise.js:649:10)
          at Promise._settlePromises (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/promise.js:725:18)
          at _drainQueueStep (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/async.js:93:12)
          at _drainQueue (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/async.js:86:9)
          at Async._drainQueues (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/async.js:102:5)
          at Immediate.Async.drainQueues (/etc/xo/xo-builds/xen-orchestra-202002022028/node_modules/bluebird/js/release/async.js:15:14)
          at runCallback (timers.js:810:20)
          at tryOnImmediate (timers.js:768:5)
          at processImmediate [as _immediateCallback] (timers.js:745:5)"
      }
      

      I tried restarting the toolstack on the host and was able to successfully take a snapshot from XCP-NG center with no issues. I'm using XCP-NG from the sources and I could try to rebuild it. Has anyone run into a similar issue?

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

        Hi,

        Please read carefully the error message. It says: "This is a XenServer/XCP-ng error".

        So it's not related directly to Xen Orchestra, but the host. That's why you should have tell us before: what XCP-ng version are you using?

        1 Reply Last reply Reply Quote 0
        • G Offline
          guiltykeyboard
          last edited by guiltykeyboard

          I'm using version 8.1 with all of the latest updates installed. The pool has two hosts currently. There was a third, but it has been removed from the pool for maintenance.

          I'm not sure why it is disagreeing with the host, because it works perfectly from XCP-NG center with no complaints. It just doesn't work when requesting the snaapshot with XO-Source.

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

            That's because Xen Orchestra isn't a clone of XCP-ng Center.

            In XO, we made the choice to automatically -by default- trying to make a coalesce snapshot. If it fails, we are automatically doing a fallback to the classical snapshot.

            However, I think this fallback should be done silently. Let's check with @julien-f about this.

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

              I don't understand the problem, XO should catch this error and automatically fall back to a normal snapshot, you should not see this error in the log.

              What version of XO are you using?

              1 Reply Last reply Reply Quote 0
              • G Offline
                guiltykeyboard
                last edited by

                X-O Server is 5.51.1 and XO-Web is 5.51.0.

                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