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

    XO tasks can't be cleared

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 2.0k 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.
    • J Offline
      jcdick1
      last edited by

      xo-server 5.64
      xo-web 5.66
      both from source

      Overnight, I have about 570 tasks in XO, and it is slowly building up. A few Async.VDI.destroy, a few host.call_plugin, but a LOT of SR.scan entries. If I click on "Cancel" it pops up with "No such task <UUID>" and changes the Cancel button to orange, but doesn't clear it out. If I go to the next page of tasks and back again, that same task is there, and the cancel button is back to red and can be pressed again, resulting in the "No such task" message again.

      Way down the list, I seem to have a [XO] VDI Export task that is hung at 99%, followed by about 14 host.call_plugin tasks that have the cancel button denied.

      Any suggestions on how to clear these out? I've tried rebooting the XO VM, I've tried restarting the tool stack on all hosts in the pool.

      Thanks!

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

        You can try cancelling the tasks using xe commands from the host's console.

        J 1 Reply Last reply Reply Quote 0
        • J Offline
          jcdick1 @Danp
          last edited by

          @Danp

          Where XO is showing a ton of SR.scan and Async.VDI.destroy tasks, xe task-list on the host shows only one "Connection to VM console" task. It's like XO is not purging completed tasks from its list.

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

            Disconnect and reconnect the server in Settings/server of XO.

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