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

    Host is locked in Maintenace mode after reboot

    Scheduled Pinned Locked Moved Compute
    6 Posts 4 Posters 408 Views 3 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.
    • jurdajrdJ Offline
      jurdajrd
      last edited by

      Hello, today I install latest patches and after reboot host is locked in maintenance mode and as I see it seems toolstack is still restarting. The host is in pool and master is working correctly without any trouble. When I use command 'xe task-list' it says The host toolstack is still intialising. Please wait.

      All SRs are connected.

      What can I do please?

      40a5ab80-6791-419e-82c1-b33c325b89cf-image.png

      Thank you for your help.

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

        Check the logs to see if they indicate a problem.

        https://docs.xcp-ng.org/troubleshooting/log-files/

        1 Reply Last reply Reply Quote 0
        • GheppyG Offline
          Gheppy
          last edited by Gheppy

          Solve the part with iSCSI and it will recover. At least that's how it was for me.
          In other words, XCP tries to connect to iSCSI and cannot do it.

          jurdajrdJ 1 Reply Last reply Reply Quote 0
          • jurdajrdJ Offline
            jurdajrd @Gheppy
            last edited by

            @Gheppy There nothing changed with iSCSI it can ping without any problem. And master is connecting sucesfully.

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

              You can see your host can't connect to your SR, please check the logs to understand what's going on there 🙂

              1 Reply Last reply Reply Quote 0
              • jurdajrdJ Offline
                jurdajrd
                last edited by

                So I found solution by myself.

                I turned off corrupted host, then on pool master I forgot corrupted host (xe host-forget uuid=aaaaaaaaa-bbbb-cccc-ddddddddddd).

                Perform a clean install of corrupted host, setup everything as it was, then patch host with XOA.

                As last step I connect it back to the pool, now everything is working fine again.

                To be honest, I do not know what happened, but everything is working now.

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