PCNS not shutting down machine

denywinarto_apc · ‎2021-06-30

I have AP9631 installed on a SUA 2200I, which is used to control PCNS for 3 windows server 2012 R2 machines.

NMC is already connected to all 3 machines and all of them are listed.

Thing is, a blackout just happened and it doesn't seem to work properly

03/19/2018	22:13:11	UPS is no longer running on battery power or output power has been turned on.
03/19/2018	21:09:13	UPS has switched to battery power.

I already set config shutdown > Runtime remaining below threshold to 900 secs, but as you can see, during 1 hour blackout there's no shutdown event happened.

I always have certificate error whenever i want to access the web page.. is it related somehow?

BillP · ‎2021-06-30

Hi,

"Last state" may work. "Always on" should have. PowerChute runs shutdown.exe with these parameters shutdown /s /f /t %delay% /d UP:6:12 /c "PowerChute Network Shutdown has initiated a system shutdown." %delay% = 60 seconds

As with any other software once the system has been powered down the software cannot control the systems behavior.

See Answer In Context

BillP · ‎2021-06-30

Hi,

Would you provide the PCNS EventLog, pcnsconfig.ini and the event.log form the NMC? The PCNS files will be found in C:\Program Files\APC\PowerChute\group1 assuming you installed to the default path.

denywinarto_apc · ‎2021-06-30

On 3/20/2018 1:55 AM, Bill said:
Hi,

Would you provide the PCNS EventLog, pcnsconfig.ini and the event.log form the NMC? The PCNS files will be found in C:\Program Files\APC\PowerChute\group1 assuming you installed to the default path.

Last night I noticed the NMC timezone isnt correct yet so i syncronized it

The related log file part should be on date 03/17/2017, but strangely none seems to mention a blackout or somehting

03/17/2018 17:00:36 UPS has switched to battery power. .3.5.1.5.4.1

03/17/2018 17:00:38 UPS is no longer running on battery power or output power has been turned on. .3.5.1.5.4.2

03/17/2018 20:50:53 PowerChute is attempting to open UDP port 3052. .3.4.9.9

03/17/2018 20:50:53 PowerChute successfully opened UDP port 3052. .3.4.9.9

03/17/2018 20:51:20 Communication has been established. .3.5.1.5.6.1

03/17/2018 20:51:20 PowerChute Network Shutdown version 4.2.0 monitoring started. .3.5.1.5.6.10

03/17/2018 20:51:21 PowerChute is attempting to open TCP port 3052. .3.4.9.9

03/17/2018 20:51:21 PowerChute is attempting to open TCP port 6547. .3.4.9.9

03/17/2018 20:51:21 PowerChute successfully opened TCP port 3052. .3.4.9.9

03/17/2018 20:51:21 PowerChute successfully opened TCP port 6547. .3.4.9.9

03/17/2018 20:51:50 Available runtime has been exceeded. .3.5.1.6.1

03/17/2018 21:18:44 PowerChute is attempting to open UDP port 3052. .3.4.9.9

03/17/2018 21:18:44 PowerChute successfully opened UDP port 3052. .3.4.9.9

03/17/2018 21:19:11 Communication has been established. .3.5.1.5.6.1

03/17/2018 21:19:12 PowerChute Network Shutdown version 4.2.0 monitoring started. .3.5.1.5.6.10

03/17/2018 21:19:13 PowerChute is attempting to open TCP port 6547. .3.4.9.9

03/17/2018 21:19:13 PowerChute is attempting to open TCP port 3052. .3.4.9.9

03/17/2018 21:19:13 PowerChute successfully opened TCP port 3052. .3.4.9.9

03/17/2018 21:19:13 PowerChute successfully opened TCP port 6547. .3.4.9.9

03/17/2018 21:19:42 Available runtime has been exceeded. .3.5.1.6.1

03/17/2018 21:36:17 PowerChute is attempting to open UDP port 3052. .3.4.9.9

03/17/2018 21:36:17 PowerChute successfully opened UDP port 3052. .3.4.9.9

03/17/2018 21:36:43 Communication has been established. .3.5.1.5.6.1

03/17/2018 21:36:44 PowerChute Network Shutdown version 4.2.0 monitoring started. .3.5.1.5.6.10

03/17/2018 21:36:45 PowerChute is attempting to open TCP port 6547. .3.4.9.9

03/17/2018 21:36:45 PowerChute is attempting to open TCP port 3052. .3.4.9.9

03/17/2018 21:36:45 PowerChute successfully opened TCP port 3052. .3.4.9.9

03/17/2018 21:36:45 PowerChute successfully opened TCP port 6547. .3.4.9.9

03/17/2018 21:37:13 Available runtime has been exceeded. .3.5.1.6.1

03/17/2018 22:42:57 PowerChute is attempting to open UDP port 3052. .3.4.9.9

03/17/2018 22:42:57 PowerChute successfully opened UDP port 3052. .3.4.9.9

03/17/2018 22:43:24 Communication has been established. .3.5.1.5.6.1

03/17/2018 22:43:24 PowerChute Network Shutdown version 4.2.0 monitoring started. .3.5.1.5.6.10

03/17/2018 22:43:24 PowerChute is attempting to open TCP port 6547. .3.4.9.9

03/17/2018 22:43:24 PowerChute is attempting to open TCP port 3052. .3.4.9.9

03/17/2018 22:43:25 PowerChute successfully opened TCP port 3052. .3.4.9.9

03/17/2018 22:43:25 PowerChute successfully opened TCP port 6547. .3.4.9.9

03/17/2018 22:43:54 Available runtime has been exceeded. .3.5.1.6.1

denywinarto_apc · ‎2021-06-30

Ah after a phone call with APC CS here i figured it out..

I mistook remaining threshold with battery on UPS..

Changed it already to Battery on UPS, gonna see next blackout if it works..

denywinarto_apc · ‎2021-06-30

Ok, it seems to work for PC that is connected using serial (havent tested for other connected PC because the blackout was too quick)

There was just one problem,

after the power is restored, my PC wont turn back on.

BIOS is set to auto turn on after power loss (cant remember the exact name)

Without PCNS it was working,

but now after being shutdown by PCNS, it wont turn back on again.. any idea?

BillP · ‎2021-06-30

Hi,

You may need to change the BIOS setting to always on See this post http://forums.apc.com/spaces/7/ups-management-devices-powerchute-software/forums/general/12332/power...

denywinarto_apc · ‎2021-06-30

Unfortunately i already set it to always on, so that cant be the solution. Could it be llast state?

BillP · ‎2021-06-30

Hi,

"Last state" may work. "Always on" should have. PowerChute runs shutdown.exe with these parameters shutdown /s /f /t %delay% /d UP:6:12 /c "PowerChute Network Shutdown has initiated a system shutdown." %delay% = 60 seconds

As with any other software once the system has been powered down the software cannot control the systems behavior.