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

    Power on function

    Scheduled Pinned Locked Moved Xen Orchestra
    52 Posts 4 Posters 8.9k Views 2 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
      dsiminiuk
      last edited by

      @olivierlambert said in Power on function:

      Weird. Can you disconnect XO from this pool, restart toolstack on master, and see if the task is popping again? I think it will, I don't see why XO would do that.

      I would remove the hosts from XO, restart toolstack, add hosts back to XO? Is this correct?

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

        Don't add host back in XO for few minutes, and check if xe task-list got the task appearing without any XO connection.

        D 1 Reply Last reply Reply Quote 0
        • D Offline
          dsiminiuk @olivierlambert
          last edited by

          @olivierlambert

          Host #2 has been powered off during these checks. I will power it on so that all pool members are available and try xe task-cancel again. Then proceed with your suggestion. Standby.

          1 Reply Last reply Reply Quote 0
          • D Offline
            dsiminiuk
            last edited by

            @olivierlambert

            OK this is interesting (host1 is master). I powered on host2 and ... the task disappeared from xe task-list and XO Tasks.

            I powered off host2 again and the task is back.

            [12:38 xcpng01 log]# xe task-list params=all
            uuid ( RO)                  : 221a86ff-ae3f-d10e-26bc-9a7b693f44f0
                        name-label ( RO): Async.host.power_on
                  name-description ( RO):
                        subtask_of ( RO): <not in database>
                          subtasks ( RO):
                       resident-on ( RO): cdb42b94-7ec6-47b4-aaef-d4c52f6bd7b3
                            status ( RO): pending
                          progress ( RO): 0.000
                              type ( RO): <none/>
                            result ( RO):
                           created ( RO): 20200708T17:37:00Z
                          finished ( RO): 19700101T00:00:00Z
                        error_info ( RO):
                allowed_operations ( RO): Cancel
                current_operations ( RO):
                      other-config (MRW):
            
            D 1 Reply Last reply Reply Quote 0
            • D Offline
              dsiminiuk @dsiminiuk
              last edited by

              I am powering up host2 again only to remove it from XO and follow your direction.

              D 1 Reply Last reply Reply Quote 0
              • D Offline
                dsiminiuk @dsiminiuk
                last edited by

                @olivierlambert

                Both servers are running in the pool.
                Both removed from XO.
                Toolstack restarted on both servers via XCP-NG Center at 12:50pm local time.
                Server communications re-established automatically in XCP-NG Center at 12:52pm.
                Pool master added and 2nd server added to XO at 12:54pm.
                No tasks are listed on either server with xe task-list.
                No tasks are listed in the XO UI.
                Powered off server 2 from the server's console screen (not XCP-NG Center or XO being the point).

                I have a task in the master on the CLI and XO again.

                uuid ( RO)                : 2f820b63-f03a-1258-1443-2f946569a4fb
                          name-label ( RO): Async.host.power_on
                    name-description ( RO):
                              status ( RO): pending
                            progress ( RO): 0.000
                
                

                The only mention of power_on in audit.log since the power up time...

                Jul  8 12:48:15 xcpng01 xapi: [20200708T17:48:15.096Z|audit||3666 |Async.host.power_on R:9802e63aaa34|audit] ('trackid=5835f391b350762fbb9dc4eb46b25614' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'host.power_on' (('host' 'xcpng02' '1139bfbc-c487-4311-8206-bbffe96ed6b1' 'OpaqueRef:426e950f-f926-490f-b598-328314aafbdc')))
                
                Jul  8 12:48:15 xcpng01 xapi: [20200708T17:48:15.183Z|audit||4625 INET :::80|task.destroy D:39825944bdf5|audit] ('trackid=5835f391b350762fbb9dc4eb46b25614' 'LOCAL_SUPERUSER' 'root' 'ALLOWED' 'OK' 'API' 'task.destroy' (('self' 'Async.host.power_on' '221a86ff-ae3f-d10e-26bc-9a7b693f44f0' 'OpaqueRef:9802e63a-aa34-4f8e-9876-94f0b3778324')))
                
                DanpD 1 Reply Last reply Reply Quote 0
                • DanpD Offline
                  Danp Pro Support Team @dsiminiuk
                  last edited by

                  @dsiminiuk You should only be adding the pool master in XO, not the slaves.

                  D 1 Reply Last reply Reply Quote 0
                  • D Offline
                    dsiminiuk @Danp
                    last edited by dsiminiuk

                    @Danp

                    http://xo/#/settings/servers is only for the pool masters not pool members?

                    I don't see where it says to not add pool members other than the master
                    https://xen-orchestra.com/docs/manage_infrastructure.html#home-view

                    I am grateful for the help but it didn't solve this issue. The task is back.

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

                      Quoting the doc:

                      Add a host
                      Just click on "Add server", enter the IP of a XenServer host (ideally the pool master if in a pool)

                      So yes, in a pool, only the master is needed to connect to all machines.

                      D 1 Reply Last reply Reply Quote 0
                      • jedimarcusJ Offline
                        jedimarcus
                        last edited by jedimarcus

                        FYI, I have a server supporting WoL which I configured and everything worked like a charm.

                        Only complaint in XOA: the Host stays yellow in Busy (shutdown) Mode but even in this mode, the Start button is available and works.

                        We configured Wake on LAN (WoL) in the BIOS and tested it with a stupid Windows Tool. WoL seems to be way more stable and proven than any other methods and the only downside I see is that it's limited to a Local Range (as it works with MAC Addresses) but I wonder how many pools don't fit in that schema.

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          dsiminiuk @olivierlambert
                          last edited by dsiminiuk

                          @olivierlambert said in Power on function:

                          Quoting the doc:

                          Add a host
                          Just click on "Add server", enter the IP of a XenServer host (ideally the pool master if in a pool)

                          So yes, in a pool, only the master is needed to connect to all machines.

                          This is problem from my perspective...

                          Host1 is the pool master and I added to Settings/Hosts.
                          I can see host1 and host2 listed in the Home/Hosts list. OK.
                          I migrated all VMs to host2. OK
                          Change pool master to host2. OK
                          If I logout of XO and back in, there are no hosts or VMs listed in Home because XO doesn't know anything about host2.

                          If XO could ask and retain the IP and credentials of the new master server when it is selected then I could see it working.

                          What if the root passwords in host1 and host2 are not identical?

                          As it is now, I must add host2 to Settings/Servers to regain control of the pool. I'm supposed to delete host1 now as well, according to the doc.

                          XCP-NG Center is what I am familiar with and that is why I added all servers to XO initially. I was expecting XO to operate the same way.

                          And I still have an active task I can't eradicate.

                          Async.host.power_on (on host2) 0%

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dsiminiuk
                            last edited by

                            Trying something new...

                            Remove all servers from XO and log out.

                            Host 1 is powered off. On host 2.

                            xe task-list
                            uuid ( RO)                : 727ecb6b-6f2e-15eb-601b-110b2478996b
                                      name-label ( RO): Async.host.power_on
                                name-description ( RO):
                                          status ( RO): pending
                                        progress ( RO): 0.000
                            
                            xe task-cancel uuid=727ecb6b-6f2e-15eb-601b-110b2478996b
                            

                            Task is still there.

                            From XCP-NG Center. Shutdown all VMs and host2 (All powered off).

                            Powered up both servers.
                            Wait 15 minutes to make sure no tasks are pending (xe task-list).

                            Logging output to file via putty of; tail -f /var/log/audit.log

                            Added host2 (master) to XO Settings/Servers.

                            The Async.host.power_on task hasn't come back.

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