PowerChute trigger event when Outletgrp is offline

[BStein_apc]

During a Maintenance on an UPS (we had to exchange the chassis) the active PowerChute started shutdown the VMs when turning off the outletgrp. This is unexpected as:

1. there is no event to define regarding the outletgroup switch to offline

2. all events were not selected to trigger anything regarding shutdown at this time

3. In a normal understanding there is no clue to start any operation when the outletgroup turns off as then no device is on power anymore (per definition...) and already down.

Is this a bug in the PowerChute Software and maybe fixed in a newer version (environment is running on latest 4 Version)? Or is this a normal behavior (then it must be fixed as it is nonsense!)

rgds Björn

[BillP]

@BStein_apc 

When PowerChute records that the UPS or assigned outlet group has been turned off, it will trigger a shutdown. This is by design as the UPS and/or outlet group being off is a critical event and is not configurable within the PowerChute UI. 

In the future to prevent the shutdown stop the PowerChute prior to turning the the outlet group off. Assuming you have installed the PowerChute VM the command to stop the PowerChute service is systemctl stop PowerChute. 

[BStein_apc]

Thank you for the answer. unfortunately I assumed that, but as I stated it is nonsense in my opinion as there is no power anymore to the devices attached to the UPS. So if they are still alive there is no sense to stop them and if not there is no possibility to do so.

Stopping PowerChute also is no option as if there are other environments managed within the same powerChute (which is possible and works as well) then these are no longer protected...

So please consider it as a feature request to move this automatism to a configurable event as all the others as well.

In such a tool there should be no "automated" automatism as it could be dangerous. As seen with this customer. fortunately there was a maintenance window and nothing worse happend.