vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machine

[Anonymous user]

Hi All, 

I have installed PCNS 4.1 to a VM to manage it's host in the cluster. Sometimes I got the message:
"vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machine"
After that If I try to open the "Host protection" I cannot connect to vCenter.
"vCenter Server is inaccessible. Please verify that the vCenter Server IP/Hostname and logon credentials are correct.."

If I open the Communications Settings within 2-3 sec the vCenter credentials turns to accepted and I can reach the "Host protection" again and
simultaneously  in the Event Log section I see "vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts"

I don't understand  what cause this kind of problem. Why lost the connection?

On an other VM I use 3.1.0 and it is working well (it is a DC VM).
However, sometimes I got the same message above but within a few minutes the communication working again.
I have tried 3.1.0 on this VM, too. But the credentials did not work. It is weird.

Any Idea what would be the problem.

Thanks in advance

Peter

[BillP]

Hi,

Check the error log in the PowerChute directory for either of these

VI SDK invoke exception:java.net.ConnectException: Connection timed out: connect
VI SDK invoke exception:java.net.ConnectException: Connection refused: connect

If there is a time out then there is a network issue that is causing the connection lose. If there is a refusal then you many need to re-enter the VCSA user name and password. 

I also recommend upgrading to PowerChute Network Shutdown version 4.2

[Anonymous user]

Hi Bill,

I am running on 4.2 sorry my mistake.

In event log:

17.10.2016 11:06:48 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
17.10.2016 10:59:30 vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machines or Hosts.

I cut here the part of error.log  maybe you see more information like me.

17-10-16 10:58:08,276 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 10:58:44,094 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - java.rmi.RemoteException: VI SDK invoke exception:java.net.SocketException: Connection reset
17-10-16 10:59:30,582 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - getVCenterServerConnection, Host 192.168.2.187 - . null
17-10-16 11:06:49,049 ERROR qtp73046176-8328 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:07:06,684 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:07:41,067 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:14,037 ERROR qtp73046176-8328 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:18,919 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:27,087 ERROR qtp73046176-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:44,404 ERROR qtp73046176-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:53,015 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:58,506 ERROR qtp73046176-63 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null
17-10-16 11:08:58,506 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareUtils - getVCenterServerVM
java.lang.NullPointerException
17-10-16 11:09:29,023 ERROR Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 - null

Thanks in advance

Peter

[BillP]

Hi,

The log show that PowerChute is attempting to connect to vCenter and cannot. The next time you see this happening stop the PowerChute daemon (/etc/init.d/PowerChute stop) and restart it (/etc/init.d/PowerChute start).

You wrote that PowerChute is running on a VM. Did you install the PowerChute OVA or is it install in VMware vMA? 

[Anonymous user]

Hi,

The environment is W2K8R2  and the PCNS 4.2 running with vmware support. The VCenter is about 1000 km far and we connect via SSLVPN 8Mbit to that network.
(I have checked the connection with ping and it showed me 4 lost packet form 1000, it looks normal, I think.)
 
I have restarted the PCNS service as you advised and I wait a few minutes but the "Host protection" showed me error. After that I opened the communication settings the small indicator disappeared within 1-2 sec and the host protection started to operate.
As the log shows the auth error appears from time to time, and the only solution to restore the connection is to open the communication settings section. (See below, all the "accessible" line based on to open Communication settings section)

I am thinking to change the settings form vCenter to hHost because the host and the UPS NMC is connected to the same switch. However I don't know is it a solution or not, because in this case I handle the Host as a single host not the part of the cluster.

Beside that the other Host is handled by PCNS 3.1.0 on an other VM. I see from time to time the connection is lost, but it is up without any manual intervention.

"log 4.2"
17.10.2016 16:34:29 vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
17.10.2016 11:06:48 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
17.10.2016 10:59:30 vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
17.10.2016 07:39:42 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
15.10.2016 10:59:21 vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
15.10.2016 10:42:11 UPS is no longer running on battery power or output power has been turned on.
15.10.2016 10:41:18 UPS has switched to battery power.
14.10.2016 12:28:51 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
12.10.2016 18:08:52 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  

"Log 3.1.0"
10/19/2016 07:03:01 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/19/2016 07:03:00 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/18/2016 17:15:38 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/18/2016 17:13:40 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/18/2016 09:09:11 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/18/2016 09:05:36 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/17/2016 14:26:07 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/17/2016 14:22:15 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/15/2016 20:29:08 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/15/2016 20:27:52 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/15/2016 20:24:06 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/15/2016 20:21:38 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/15/2016 19:59:00 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/15/2016 19:57:44 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/15/2016 19:53:59 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.
10/15/2016 19:52:15 Cannot connect to vCenter Server. PowerChute may not be able to issue commands to Virtual Machines or Hosts.  
10/15/2016 10:42:12 UPS is no longer running on battery power or output power has been turned on.
10/15/2016 10:41:19 UPS has switched to battery power.

Many thanks

Peter

[BillP]

Peter,

The logs indicate that PowerChute is attempting to connect to vCenter but it is either not able to due to the network or due to vCenter refusing the connection. The next time you see the issue on PCNS 4.2 stop the daemon and put PowerChute into debug mode then restart PowerChute. See FAQ FA230514 for assistance with putting PowerChute into debug mode. If as you wrote PowerChute still cannot connect to vCenter let it run for 5 minute then open the communication setting page and reset PowerChute. Once communication has been established stop PowerChute and send the debug.log file for review also take PowerChute out of debug mode before restarting it. The debug.log file will be in PowerChute/group1 directory.

[Anonymous user]

Dear Bill,

I set the debug mode, and start PCNS and I wait.
After that I login to PCNS and open "Host protection". The problem appeared. I open Communication settings and wait until the credentials was accepted and opened the "Host protection" again and it worked.I enclosed the debug log as you said.
Thanks
Peter

[BillP]

Peter,

The error log has multiple entries of 

21-10-16 09:09:49,645 DEBUG Thread-2 com.apcc.m11.components.WebServer.util.virtualization.VMWareConnection - Unable to connect to vCenter Host 192.168.2.187 -
com.vmware.vim25.NoPermission

This does not explain why when you enter the credentials they are accepted but there is a problem when PCNS attempts to connect. To resolve you could create a PCNS user on VCSA and the host/s and have PCNS use that account. 

[Anonymous user]

Bill,

If I understand correctly you prefer to create a user on vCenter instead of use windows credentials?

[BillP]

Peter,

My suggestion is based on the fact that VCSA is rejecting the credentials you are using now. In my lab I have VCSA running on Windows Server 2012 VM that is on 1 of my 3 ESXi 5.5 hosts. I created a PCNSTESTER account on the Windows Server with admin privileges. I then added that user to vCenter and each of the hosts with admin privileges. We have FAQ FA241010 on the subject. If VCSA is running on Linux you should create a user on that VM and then add the user to vCenter and each host. 

[Anonymous user · Accepted solution]

Bill,

We use AD so we cannot use local users on VM  which can reach the vCenter server.
I add a new AD user to the administrator group and the vmware_admin group too.
I replace the user credentials in PCNS, but the situation is the same.

24.10.2016 21:01:59 vCenter Server authentication error. PowerChute may not be able to issue commands to Virtual Machines or Hosts.
24.10.2016 14:29:34 vCenter Server is accessible. PowerChute will be able to issue commands to Virtual Machines or Hosts.

I suppose the issue based on the user is AD user. On the other VM where this problem is not exist the VM is DC.
Maybe that is the reason why on that VM is working and on this not. It's only a assumption on my side.