The vSphere Client is only reporting "Find entity by IP" and "Find entity by DNS" again and again once the shutdown gets called by PCNS but nothing actually happens, no Host shutdown gets initiated thus no VM gets shutdown either.Īs a "workaround" i have now setup PCNS to call the actual shutdown bash file /opt/APC/PowerChute/group1/bin/shutdown explicit as a Run command under Shutdown Settings in the PCNS frontend.and i am pretty certain that this shouldn't be required to get it to work.Īs i originally wrote i am running PCNS on vMA (as a service, installed using pcns310ESXi.tar downloaded on July 7 2014) and not the PCNS appliance, as i make use of the vMA anyway. The problem just hit me on a setup i did a while ago, and never truly tested (yeah, yeah, shame on me.never ever trust a Whitepaper) with the site having a one hour lasting power-outtake this morning and none of the configured VMs were gracefully shutdown and the host just turning off after sucking the batteries dry. The exact same Problem still exists and the announced patch has yet to be released, or at least i am not seeing anything over at apc.com. for ESX(i) licensed and free versionĪs much as i hate resurrecting old topics but as of today, running:
#3.0.1 POWERCHUTE SOFTWARE DOWNLOAD HOW TO#
The following Kbase provides details on how to perform ESXi host shutdown for the free version: PowerChute Network Shutdown does not support the free version of ESXi. attempting to shutdown the Free/Unlicensed version of ESXi.Ĭan you confirm if it is the free version of ESXi 5.5 or a licensed version? If licensed, can you specify the license type? This error - "" usually points to a licensing issue e.g.
Can you check if the following errors appear in /opt/APC/PowerChute/group1/error.log:ĮRROR Thread-35 .Shutdowner.ShutdownSequencer - performShutdownForESXiStandaloneConfigurationĮRROR pool-2-thread-1 .Shutdowner.CheckIfCriticalEventActive - processCriticalEventExceptClusterMode
0 kommentar(er)
