PowerChute Network Shutdown 4.2 Not shutting down host

[Anonymous user]

Hello,

I have kind of same behaviour as Roel had on this post: http://forums.apc.com/spaces/7/ups-management-devices-powerchute-software/forums/general/11293/power...

Here is what happens:

When Low Battery event occurs, PCNS puts server2 in maintenance mode and shuts correctly VMs on it. But then server1 (who hosts vm-vcenter and PCNS VM stops) is able to shut down vm-vcenter but maintenance mode is cancelled...

Normally server2 is shut down correctly, sometimes it doesn't work...

Here are the logs:

12/06/2017    15:04:16    Low-battery condition has occurred.
12/06/2017    15:04:16    UPS critical event: Low Battery.
12/06/2017    15:04:16    Shutdown sequence started on Hosts server2.domain, server1.domain in response to UPS critical event: Low Battery.
12/06/2017    15:04:18    Starting Maintenance Mode Task on Host server2.domain.
12/06/2017    15:04:18    Shutting down VMs on Host server2.domain.
12/06/2017    15:04:18    Starting Maintenance Mode Task on Host server1.domain.
12/06/2017    15:04:18    Shutting down VMs on Host server1.domain.
12/06/2017    15:04:35    Low-battery condition solved.
12/06/2017    15:04:35    UPS critical event: Low Battery resolved on Hosts server2.domain, server1.domain.
12/06/2017    15:04:36    Low-battery condition has occurred.
12/06/2017    15:06:18    Host server2.domain has successfully entered maintenance mode.
12/06/2017    15:06:18    Exit maintenance mode on Host server1.domain.
12/06/2017    15:06:19    Shutting down vCenter Server VM vm-vcenter.
12/06/2017    15:06:20    Maintenance Mode Task cancelled on Host server1.domain as VCSA VM is shutting down.
12/06/2017    15:07:20    Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
12/06/2017    15:07:20    Shutting down Host server2.domain.
12/06/2017    15:07:49    Low-battery condition solved.
12/06/2017    15:09:28    Attempting to start vCenter Server VM vm-vcenter.
12/06/2017    15:11:36    vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
12/06/2017    15:12:38    Low-battery condition has occurred.
12/06/2017    15:12:38    UPS critical event: Low Battery.
12/06/2017    15:12:38    Shutdown sequence started on Hosts server2.domain, server1.domain in response to UPS critical event: Low Battery.
12/06/2017    15:12:39    Starting Maintenance Mode Task on Host server1.domain.
12/06/2017    15:12:39    Shutting down VMs on Host server1.domain.
12/06/2017    15:12:39    Low-battery condition solved.
12/06/2017    15:12:39    UPS critical event: Low Battery resolved on Hosts server2.domain, server1.domain.
12/06/2017    15:12:47    Low-battery condition has occurred.
12/06/2017    15:12:47    Low-battery condition solved.
12/06/2017    15:12:48    Low-battery condition has occurred.
12/06/2017    15:14:39    Exit maintenance mode on Host server1.domain.
12/06/2017    15:14:42    Shutting down vCenter Server VM vm-vcenter.
12/06/2017    15:14:43    Maintenance Mode Task cancelled on Host server1.domain as VCSA VM is shutting down.
12/06/2017    15:15:43    Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
12/06/2017    15:15:46    Shutdown Host failed for Host server2.domain.
12/06/2017    15:27:37    UPS is no longer running on battery power or output power has been turned on.
12/06/2017    15:27:37    Low-battery condition solved.

I have checked those settings:

isPCNSonVM = true

shutdownCommand = /opt/APC/PowerChute/group1/bin/shutdown

Why am I unable to shut down my host server1?

[BillP]

Hi,

Please follow these instruction to put PowerChute into debug mode and the run a shutdown test. 

1. Stop the PowerChute daemon. In the command prompt, type:
service PowerChute stop or sudo service PowerChute stop

2. Navigate to: /opt/APC/PowerChute/group1

3. Create a backup of error.log by copying it to another directory and renaming it to error.log.backup

4. Create a backup of log4j2.xml by copying it to another directory or renaming it to log4j2.xml.backup

5. Using a text editor, edit log4j2.xml and change the line

Root level="error"
To
Root level="debug"

6. Restart the PowerChute daemon. In the command prompt, type:

service PowerChute start or sudo service PowerChute start

When PowerChute is restarted it will write debug information to error.log file.

When debugging is completed, stop the PowerChute daemon, copy the contents of  log4j2.xml.backup  into llog4j2.xml (to reset the values changed in step 5) and backup error.log by copying it to a new file naming it error-debug.log.

Once the test is completed attach the files error-debug.log, pcnsconfig.ini, EventLog.txt, VirtualizationFileStore.properties, javaVersionFile.log

If you do not feel comfortable attaching the files to this post please contact local support for assistance. You will find local support contact information at this link http://www.apc.com/us/en/support/contact-us/index.jsp You will need to select the proper country. 

[Anonymous user · Accepted solution]

Hello Bill,

Thanks for you answer, I had already enabled the debug mode so I sent those informations to the APC local team.