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

    Xen Orchestra VM Stats not showing

    Scheduled Pinned Locked Moved Solved Management
    4 Posts 3 Posters 360 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.
    • D Offline
      dguy313
      last edited by olivierlambert

      I'm using Xen Orchestra Community Edition.

      When I click on Stats for VM's it simply says "No Stats".

      It appears the issue is only with XO as I can use XCP-NG Center v20.04.01 and see stats.

      When I click on XO logs i get this error:

      vm.stats
      {
        "id": "bd624d23-6d7d-a1f0-791d-541e91351bb5",
        "granularity": "seconds"
      }
      {
        "message": "unusable",
        "name": "TypeError",
        "stack": "TypeError: unusable
          at /opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:224:34
          at Promise._execute (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/debuggability.js:384:9)
          at Promise._resolveFromExecutor (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/promise.js:518:18)
          at new Promise (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/bluebird/js/release/promise.js:103:10)
          at consume (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:212:10)
          at BodyReadable.text (/opt/xo/xo-builds/xen-orchestra-202409281449/node_modules/undici/lib/api/readable.js:111:12)
          at file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xapi-stats.mjs:258:39
          at XapiStats._getAndUpdateStats (file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xapi-stats.mjs:319:18)
          at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202409281449/@vates/task/index.js:169:22)
          at Task.run (/opt/xo/xo-builds/xen-orchestra-202409281449/@vates/task/index.js:153:20)
          at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202409281449/packages/xo-server/src/xo-mixins/api.mjs:402:20)"
      }
      
      1 Reply Last reply Reply Quote 0
      • A Offline
        Andrew Top contributor @dguy313
        last edited by

        @dguy313 Sunday's XO commit 030b3 solves the issue for me.

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

          Hi,

          It's a known issue (see this prior thread). Should be fixed soon.

          Dan

          1 Reply Last reply Reply Quote 1
          • D Offline
            dguy313
            last edited by

            Ok thanks!

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              Andrew Top contributor @dguy313
              last edited by

              @dguy313 Sunday's XO commit 030b3 solves the issue for me.

              1 Reply Last reply Reply Quote 2
              • olivierlambertO olivierlambert marked this topic as a question on
              • olivierlambertO olivierlambert has marked this topic as solved on
              • First post
                Last post