PCNS 3.1 no longer requires you to add the ESXi host using vifp addserver command.
Can you enable debug logging in PCNS 3.1 as follows:
1. sudo service PowerChute stop.
2. Edit /opt/APC/PowerChute/group1/log4j.xml using sudo vi and change:
<priority value="error" />
<appender-ref ref="rollingFile" />
<priority value="debug" />
<appender-ref ref="rollingFile" />
3. Save log4.xml and re-start the daemon - sudo service PowerChute start.
4. Try to shutdown the UPS again.
Attach a copy of /opt/APC/PowerChute/group1/error.log
Can you check if the following errors appear in /opt/APC/PowerChute/group1/error.log:
ERROR Thread-35 com.apcc.m11.components.Shutdowner.ShutdownSequencer - performShutdownForESXiStandaloneConfiguration
ERROR pool-2-thread-1 com.apcc.m11.components.Shutdowner.CheckIfCriticalEventActive - processCriticalEventExceptClusterMode
This error - "com.vmware.vim25.RestrictedVersion" usually points to a licensing issue e.g. attempting to shutdown the Free/Unlicensed version of ESXi.
Can you confirm if it is the free version of ESXi 5.5 or a licensed version? If licensed, can you specify the license type?
PowerChute Network Shutdown does not support the free version of ESXi. The following Kbase provides details on how to perform ESXi host shutdown for the free version:
We have discovered an issue in PCNS 3.1 that affects Standalone ESX/ESXi hosts only. NB: This does not occur if you are using the Managed by vCenter Server option.
PowerChute opens an API session to communicate with the ESX/ESXi host that later times out and PowerChute fails to re-establish the session. This prevents PowerChute from issuing a shutdown command to the Host when a critical UPS event occurs. A fix has been identified and an update to address this issue will be published on the APC Web site shortly. v3.0.1 should be used for Standalone ESXi hosts until the update has been released.
I am running ESXi 5.1 with a vMA along with vCenter Server 5.1.
I have PCNS 3.0.1 installed on the vMA.
I do not recall seeing or selecting an option for Managed by vCenter Server.
The current installation is working as when there is a critical battery event, the VMs do an orderly shutdown.
My goal is to upgrade to vSphere 5.5.
APC support indicted that vSphere / ESXi 5.5 is not supported with PCNS but didn’t say it would not work.
Is it possible to upgrade to 5.5 and use PCNS to shutdown the VMs if the batteries reach the critical threshold?
Yes it should be possible to upgrade to vSphere 5.5 and use PCNS to shutdown the VMs. You should be able to use PCNS 3.0.1 to achieve this.
PCNS 3.1 is the latest version and provides support for HA Clusters.
As much as i hate resurrecting old topics but as of today, running:
* ESXi 5.5 (licensed)
* vMA 5.5
* PCNS 3.10
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...
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 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.
As 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.
I just deployed PCNS 3.1 Appliance (not powered up yet) and also have a vMA running on ESXi 5.5 U1 build 1881737 with plans to move to ESXi U2.
I was going to shutdown the vMA and bring the PCNS Appliance on-line to handle the automated shutdown.
What problem are you referring to that requires a patch?
The issue is outlined in the following Kbase FAQ - FA222090
It has since been fixed - This update was included as part of the main product on the Software/Firmware downloads page on February 17th 2014 so any downloads since this date are not exposed to this issue.
Looks like I need to then download and apply the patch PCNS3.1.0EN.tar.gz listed in the FAQ?
If you downloaded the Appliance before Feb 17th then yes you'll need to install the patch or download the Appliance again to replace your existing copy.
@defkev: FindByIP/FindByDNSName: Could you attach a copy of error.log, pcnsconfig.ini and EventLog.txt please? These are located in /opt/APC/PowerChute/group1 folder on vMA.
The /opt/APC/PowerChute/group1/bin/shutdown is no longer used in 3.1 for shutting down the ESXi host.
The one i have unnzippd is dated 2/4/14.
What is in the logs??
The affected version is build 4512 (See About Box in PowerChute UI).
The fixed version is build 4844. The fixed version of the Appliance is available to download from the APC Software/Firmware downloads page.
The request for the logs was in response to the comments posted by user defkev on Sep 11, 2014 1:12 AM.
i see the new appliance is dated 9/10/14 at the APC site
It would be nice if APC would let users know when thee are new patches or potential issues once they are discovered