11.components.Shutdowner.Hosts.ESXManagedHost - Failed to take host out of maintenance mode: 192.168.139.6
12-06-18 10:35:03,067 ERROR pool-185-thread-2 com.apcc.m11.components.Shutdowner.Hosts.ESXManagedHost - Failed to take host out of maintenance mode: 192.168.139.4
I would check the permissions. Once PCNS powers vCenter off it will then take the host out of maintenance mode to allow the host to start up and start PCNS when AC is restored. When vCenter is off line if permissions are not correct PCNS will not be able to communicate with the host and therefore not take it out of maintenance mode.
I made sure permissions were set correctly by creating the accounts on each host and configuring PCNS to use that account in case vCenter is not available. Is it possible that the host running PCNS and vCenter is shutting down before the one that fails?
Bill Here's a screenshot of vCenter showing the PowerChuteAdmin user I created. This user also exists on the VM running vCenter (Windows) and also on each individual ESXi host.
The shutdown process is
1 - put hosts into maintenance mode
2 - shutdown VMs and vApps
3 - shutdown vCenter Server
4 - Shutdown hosts starting with the host not running PCNS
Host 139.6 should remain in maintenance mode until restarted. Host 136.4 should be taken out of maintenance mode to allow it to restart when AC is restored which in turn will allow PCNS to restart.
Have you put PCNS into debug mode and reviewed the error.log to see what errors are posted. If you need assistance putting PCNS into debug mode see Schneider Electric FAQ FA230514
The error.log file shows a permissions issue
I can log in to 139.4 just fine with the PowerChuteAdmin user.
Here's the event log:
So after you said it was a permission issue, I kept digging further and discovered that this part
PowerChute Security"The Username and Authentication Phrase are used to authenticate communications between PowerChute and the NMC. Therefore, you must set these values to be the same in both PowerChute and the NMC."
So it appears that the user in the NMC must be the same as the user in PowerChute appliance. If I stuck to the default configuration of the user apc I would probably not have ran into this issue but I insisted on creating my own user and forgot to change it in the PowerChute Security section.
Thank you very much for your help Bill .
Choose a location
There are no forums in this space.