Issue on vCenter shutdown with virtual powerchute and vCenter

[Anonymous user]

Our infrastructure is based on three hosts managed by a virtual vCenter hosted on host 1, just as powerchute virtual appliance which manages shutdown.

When powerchute sends shutdown signal to all hosts, host 2 is correctly switched off with all VM gently shutted down, host 3 remains in maintenance mode (even with VM's shutted down) while host 1 is shutdown having powerchute VM powered off without guest-shutdown.

It seems that vCenter cannot be correctly stopped and host 3 cannot be shutdown.

It's not a permission issue: we are having tests using directly administrator@vsphere.local to avoid any trouble using domain admins.

What can be wrong?

Thanks in advance.

[BillP]

Hi,

Please follow the instruction in Schneider Electric FAQ FA230514 to put PowerChute into debug mode. Then run a shut down test. After the test has completed follow the instruction in Schneider Electric FAQ FA241061 to gather the needed troubleshooting files and attach the file to this post.

If you are not comfortable with attaching the files to the post please contact local support and they will assist you with the troubleshooting.

[BillP · Accepted solution]

Hi,

The event logs shows 

09/01/2017 16:40:45 Shutdown Host failed for Host 192.168.1.121. .3.4.9.9

09/01/2017 16:40:51 Shutdown Host failed for Host 192.168.1.123. .3.4.9.9

09/01/2017 16:40:58 Shutdown Host failed for Host 192.168.1.120. .3.4.9.9

In the error log PCNS reports 

01-09-17 16:40:45,100 ERROR Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): 192.168.1.121

01-09-17 16:40:45,100 DEBUG Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - com.vmware.vim25.InvalidLogin

01-09-17 16:40:51,080 ERROR Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): 192.168.1.123

01-09-17 16:40:51,081 DEBUG Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - com.vmware.vim25.InvalidLogin

01-09-17 16:40:58,732 ERROR Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to log directly into host (NoPermission or InvalidLogin): 192.168.1.120

01-09-17 16:40:58,732 DEBUG Thread-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - com.vmware.vim25.InvalidLogin

When vCenter Server Connection is not available PowerChute will attempt to connect directly to each ESXi host to perform VM shutdown. This requires a shared user account (see section on creating shared user accounts) to be present on each of the ESXi hosts. If PowerChute cannot connect to the ESXi hosts the following exceptions may appear in the error.log: com.vmware.vim25.NoPermission com.vmware.vim25.InvalidLogin 

Solution: Verify that the vCenter Server User Account configured in PowerChute can access each of the ESXi hosts by connecting directly to each host using the vSphere client. If the connection is lost, add the user account to each ESXi host. If the connection is successful verify that the user account has “Administrator” permissions.