Lost Connection to PCNS on vMA

[stanj_apc]

I tried to  logon to PNCS running on our ESXi 5.0 vMA  https://128.xx.xx.xx:6547/ and get,,,,,,,,,

Internet Explorer cannot display the webpage

I can ping the IP the IP of the vMA ..128.xx.xx.xx.

I last logged on in December and it worked.

I  reconfigured the network settings to amke sure it was not a network issue and rebooted the vMA.

still cannot get to PCNS.

Any idea why I lost connection to PCNS on vMA?

thanks

[BillP]

Hi,

I suggest uninstalling and then reinstalling PCNS. If it continues to stop, assuming you installed to the default path look in /opt/APC/PowerChute/group1/EventLog.txt The command would be

more /opt/APC/PowerChute/group1/EventLog.txt

It should list / show why PCNS is stopping.

[stanj_apc]

ok,  i  do not see in the current log what is causing the shutdown..below is the log ..current status is stopped..

03/21/2013      06:43:29        PowerChute successfully opened UDP port 3052.   .3.4.9.9

03/21/2013      06:43:30        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

03/21/2013      06:43:31        PowerChute successfully opened TCP port 3052.   .3.4.9.9

03/21/2013      06:43:32        PowerChute successfully opened TCP port 6547.   .3.4.9.9

03/29/2013      13:51:48        Communication has been established      .3.5.1.5.6.1

03/29/2013      13:51:50        PowerChute successfully opened UDP port 3052.   .3.4.9.9

03/29/2013      13:51:51        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

03/29/2013      13:51:52        PowerChute successfully opened TCP port 3052.   .3.4.9.9

03/29/2013      13:51:53        PowerChute successfully opened TCP port 6547.   .3.4.9.9

03/29/2013      15:03:46        Communication has been established      .3.5.1.5.6.1

03/29/2013      15:03:48        PowerChute successfully opened UDP port 3052.   .3.4.9.9

03/29/2013      15:03:49        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

03/29/2013      15:03:50        PowerChute successfully opened TCP port 3052.   .3.4.9.9

03/29/2013      15:03:50        PowerChute successfully opened TCP port 6547.   .3.4.9.9

03/29/2013      16:48:05        Communication has been established      .3.5.1.5.6.1

03/29/2013      16:48:06        PowerChute successfully opened UDP port 3052.   .3.4.9.9

03/29/2013      16:48:07        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

03/29/2013      16:48:08        PowerChute successfully opened TCP port 3052.   .3.4.9.9

03/29/2013      16:48:09        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      09:10:28        Communication has been established      .3.5.1.5.6.1

04/02/2013      09:10:30        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      09:10:31        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      09:10:31        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      09:10:32        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      11:56:36        Communication has been established      .3.5.1.5.6.1

04/02/2013      11:56:39        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      11:56:40        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      11:56:40        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      11:56:41        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      11:59:00        Communication has been established      .3.5.1.5.6.1

04/02/2013      11:59:02        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      11:59:03        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      11:59:03        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      11:59:04        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      12:00:50        Communication has been established      .3.5.1.5.6.1

04/02/2013      12:00:53        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      12:00:54        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      12:00:55        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      12:00:55        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      12:05:20        Communication has been established      .3.5.1.5.6.1

04/02/2013      12:05:23        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      12:05:24        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      12:05:24        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      12:05:25        PowerChute successfully opened TCP port 6547.   .3.4.9.9

04/02/2013      12:09:42        Communication has been established      .3.5.1.5.6.1

04/02/2013      12:09:45        PowerChute successfully opened UDP port 3052.   .3.4.9.9

04/02/2013      12:09:46        PowerChute Network Shutdown version 3.0.1 started       .3.5.1.5.6.10

04/02/2013      12:09:47        PowerChute successfully opened TCP port 3052.   .3.4.9.9

04/02/2013      12:09:47        PowerChute successfully opened TCP port 6547.   .3.4.9.9

[BillP]

Hi,

You are right. The log is not capturing the shutdown so that indicates something on the vMA is causing the daemon to crash/stop with no warning. You can look in /var/log/messages to see if the system is capturing the event. I suggest using the command tail -50 /var/log/messages | more to view just the last 50 entries in the log 1 screenful at a time. The other suggestion is to uninstalling / removing the vMA, re-install it, and then install PCNS.

[stanj_apc]

below is the log after I restarted,,,

I can uninstall/ remove the vMA, re-install it, and then install PCNS,,but what happens if this occurs again at a critical pwr outage?

-----

vi-admin@redd-vma:/opt/APC/PowerChute/group1> sudo /etc/rc.d/init.d/PowerChute status

PowerChute is running ...

vi-admin@redd-vma:/opt/APC/PowerChute/group1>

vi-admin@redd-vma:/opt/APC/PowerChute/group1>

vi-admin@redd-vma:/opt/APC/PowerChute/group1> sudo /etc/rc.d/init.d/PowerChute status

PowerChute is running ...

vi-admin@redd-vma:/opt/APC/PowerChute/group1> sudo /etc/rc.d/init.d/PowerChute status

PowerChute is stopped

Apr  8 08:24:58 redd-vma -- MARK --

Apr  8 08:44:58 redd-vma -- MARK --

Apr  8 09:04:58 redd-vma -- MARK --

Apr  8 09:04:58 redd-vma syslog-ng[1568]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=542', processed='center(received)=510', processed='destination(messages)=507', processed='destination(mailinfo)=2', processed='destination(mailwarn)=1', processed='destination(localmessages)=0', processed='destination(newserr)=0', processed='destination(mailerr)=0', processed='destination(cron)=1', processed='destination(netmgm)=0', processed='destination(warn)=14', processed='destination(console)=7', processed='destination(null)=0', processed='destination(mail)=3', processed='destination(xconsole)=7', processed='destination(firewall)=0', processed='destination(acpid)=0', processed='destination(newscrit)=0', processed='destination(newsnotice)=0', processed='source(src)=510'

Apr  8 09:24:58 redd-vma -- MARK --

Apr  8 09:44:58 redd-vma -- MARK --

Apr  8 10:04:58 redd-vma -- MARK --

Apr  8 10:04:58 redd-vma syslog-ng[1568]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=546', processed='center(received)=514', processed='destination(messages)=511', processed='destination(mailinfo)=2', processed='destination(mailwarn)=1', processed='destination(localmessages)=0', processed='destination(newserr)=0', processed='destination(mailerr)=0', processed='destination(cron)=1', processed='destination(netmgm)=0', processed='destination(warn)=14', processed='destination(console)=7', processed='destination(null)=0', processed='destination(mail)=3', processed='destination(xconsole)=7', processed='destination(firewall)=0', processed='destination(acpid)=0', processed='destination(newscrit)=0', processed='destination(newsnotice)=0', processed='source(src)=514'

Apr  8 10:24:58 redd-vma -- MARK --

Apr  8 10:45:01 redd-vma -- MARK --

Apr  8 10:48:14 redd-vma sshd[14122]: Accepted password for vi-admin from 128.244.200.27 port 6493 ssh2

Apr  8 10:56:16 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute start

Apr  8 11:03:40 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute status

Apr  8 11:03:58 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute start

Apr  8 11:04:02 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute status

Apr  8 11:04:58 redd-vma syslog-ng[1568]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', processed='center(queued)=554', processed='center(received)=522', processed='destination(messages)=519', processed='destination(mailinfo)=2', processed='destination(mailwarn)=1', processed='destination(localmessages)=0', processed='destination(newserr)=0', processed='destination(mailerr)=0', processed='destination(cron)=1', processed='destination(netmgm)=0', processed='destination(warn)=14', processed='destination(console)=7', processed='destination(null)=0', processed='destination(mail)=3', processed='destination(xconsole)=7', processed='destination(firewall)=0', processed='destination(acpid)=0', processed='destination(newscrit)=0', processed='destination(newsnotice)=0', processed='source(src)=522'

Apr  8 11:04:58 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute status

Apr  8 11:05:31 redd-vma sudo: vi-admin : TTY=pts/0 ; PWD=/opt/APC/PowerChute/group1 ; USER=root ; COMMAND=/etc/rc.d/init.d/PowerChute status

vi-admin@redd-vma:/opt/APC/PowerChute/group1>

[stanj_apc]

Hi Angela,

I have tried some of the commands Bill provided. So far, I cannot see the issue.

His suggestion is to uninstall PCNS from the vMA and reinstall.

However, this will not narrow down the cause of PCNS shutting down.

The last info I have is—I can start PCNS and it stays up for about 1 minutes,,

Here is what I did:

----ssh to vMA

login as: vi-admin

Welcome to vSphere Management Assistant

vi-admin password:

Last login: Mon Apr 8 10:48:14 2013 from novinsj1-wd4

vi-admin@redd-vma:~> sudo /etc/rc.d/init.d/PowerChute status

vi-admin's password:

PowerChute is stopped

vi-admin@redd-vma:~>

vi-admin@redd-vma:~> sudo /etc/rc.d/init.d/PowerChute start

PowerChute Network Shutdown, v3.0.1

Copyright (c) 1999-2012, Schneider Electric. All Rights Reserved.

Startup completed.

vi-admin@redd-vma:~> sudo /etc/rc.d/init.d/PowerChute status

PowerChute is running ...

vi-admin@redd-vma:~>

####### Logged into PCNS on vMA ,,while logged in, lost connection #######

vi-admin@redd-vma:~> sudo /etc/rc.d/init.d/PowerChute status

PowerChute is stopped

vi-admin@redd-vma:~>

thanks

Stan

[BillP]

Hi stanj - unfortunately, I feel out of my league here on this topic. Bill P. - got any other ideas that Stan could try in order to get to the root cause of the PowerChute service stopping?

[BillP]

stanj,

Have you uninstalled and reinstalled the vMA? Since the daemon is just stopping it leads me to believe the issue is with the vMA. Another possibility could be an issue/conflict with java. When you installed PCNS did you select to use the bundled java or did you point to pre-installed java? If you pointed to pre-installed java I suggest uninstalling PCNS and reinstall it using the bundled java.

[stanj_apc]

I have not uninstalled the vMA.  That means reinstalling vMA and PCNS.  When I installedPCNS, I followed the section "Installing PowerChute Network Shutdown" in the Overview of PowerChute Network Shutdown Installation for ESXi.  I don't recall pre-installing java so I am guessing it was the bundled java.  However, if I login to the vMA and issue $ rpm -q jre,,,I get back that it jre is not installed,,,,,  but as I said, PCNS starts and then dies after about 30-45 seconds.

[stanj_apc]

I found an firmware update the APC site for the NMC called - powernet407.mib.

It looks like an update?

I have it on my PC but whenI try to ftp it over to the NMC, I get a time out..

How do I get the file over to the NMC and apply the update?

[stanj_apc]

update,,i found and downloaded

apc_hw05_aos517_sy517_bootmon102.exe

extracted the files and FW_Upgrade_R2.exe.

this updated the firmware to 5.1.7,,

but the PCNS on the vMA is still stopping after a restart..

[BillP]

I did not think this issue had to do with the firmware but what type of UPS are you using because that application (apc_hw05_aos517_sy517_bootmon102.exe) is for single phase symmetra, not Smart UPS. Just wanted to check.

This may be a generic issue not related to PowerChute also - where something else you have installed is interfering with this service.

[stanj_apc]

I tried to  logon to PNCS running on our ESXi 5.0 vMA  https://128.xx.xx.xx:6547/ and get,,,,,,,,,

Internet Explorer cannot display the webpage

I can ping the IP the IP of the vMA ..128.xx.xx.xx.

I last logged on in December and it worked.

I  reconfigured the network settings to amke sure it was not a network issue and rebooted the vMA.

still cannot get to PCNS.

Any idea why I lost connection to PCNS on vMA?

thanks

[BillP]

Can you confirm the PCNS service is actually running on the VMA? Have you tried a different web browser and computer?

[stanj_apc]

i stopped and started the service and still cannot connect.

i tried firefox and IE from different PCs and VMs.

what is the command to see if PCNS is running on the vMA?

when I connect to the UPS via COM port/cable and login, I can ping the vMA..

are the log files on the vMA that may show what is going on?

thanks

[BillP]

Hi stanj -

Bill P. will help us with some commands to try. Thanks Bill.

[BillP · Accepted solution]

Hi,

To check the status of PCNS on vMA 5.0 run this command

sudo /etc/rc.d/init.d/PowerChute status (the available options are stop, start, status)

The command will return PowerChute is running, PowerChute is stopped, or command not found. If command not found is returned that indicates the software has been uninstalled. If the process is running and you cannot connect you need to verify the ip address of the vMA and check to be sure tcp port 6547 is not being blocked.