Technical FAQs

Ask a Question

PowerChute Network Shutdown 3.1 fails to shut down a Standalone VMware Host when critical event occurs.

When PowerChute Network Shutdown v3.1 is configured using the Standalone VMware Host option it fails to shut down an ESX/ESXi host when a critical UPS event occurs.

Product Line:
PowerChute Network Shutdown (PCNS) version 3.1 build 4512 - ESXi, Virtual Appliance

PowerChute v3.1 is deployed as a Virtual Appliance or installed on vMA to monitor Standalone VMware Hosts that are not managed by vCenter Server. Hosts that are managed by vCenter Server are not affected.
ESX 4.x
ESXi 4.x
ESXi 5.x

Software issue. 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.

Symptoms: The following error appears in /opt/APC/PowerChute/group1/error.log when a failed shutdown attempt occurs -

27-01-14 20:46:44,311 ERROR pool-1-thread-4 com.apcc.m11.components.WebServer.util.VirtualizationUtils - getVirtualMachineOnWhichPCNSInstalledRuntimeFaultcom.vmware.vim25.NotAuthenticated


Update to PCNS version 4.x


Download the Update attached and follow these instructions:

1. Transfer the file to a folder on the vMA or PowerChute Virtual Appliance using SCP or SFTP (see FA159776 ). If you cannot access the appliance using SCP or SFTP see FA222181
2. SSH to the vMA or Virtual Appliance.
3. Open a terminal prompt and change directory to the location of the PCNS3.1.0EN.tar.gz file.
4. Enter "sudo sh" and enter root password to switch to a root prompt or use sudo for each of the individual commands in steps 5 to 9 below.
5. Enter "gunzip PCNS3.1.0EN.tar.gz"
6. Enter "tar xvf PCNS3.1.0EN.tar"
7. Enter "cd PCNS3.1.0EN"
8. Enter "chmod +x"
9. Enter "./"

The InstallUpdate script will stop the PowerChute daemon, replace pcns.jar in the /opt/APC/PowerChute/group1/comp folder and re-start the daemon.

NOTE: 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.



Was this helpful?
What can we do to improve the information ?