"Could not check if VC is alive." and "Could not log out from VC" events in collector error logs for VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

You see errors in the VCF Operations for Networks Collector logs like "Connection close attempt on dead connection failed with message : Could not log out from VC"

 

Example log records (In directory /var/log/arkin/collector/")

 

2024-12-30T14:12:24.771Z ERROR vcenter.southbound.VCConnectionEntity VCENTER_###.###.###_Esxcli_OpMgr-0 isAlive:207 Could not check if VC is alive. java.rmi.RemoteException: Exception caught trying to invoke method CurrentTime_ nested exception is:

2024-12-30T14:12:24.772Z ERROR dataproviders.dsconnectionmanagement.ConnectionEntityPool VCENTER_###.###.###_Esxcli_OpMgr-0 getAliveConnection:146 Connection close attempt on dead connection failed with message : Could not log out from VC

 

 

In the UI for the VCF Operations for Networks Platform node in the Dashboard view, you may see the alert "Data collection failed due to an error.  Please wait for some time."

 

 

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

 

Environment

VCF Operations for Networks 6.x

 

Cause

Data Source connection authentication information that has been cached on the VCF Operations for Networks collector needs to be refreshed via a Collector VM reboot.

Resolution

Reboot the  VCF Operations for Networks Collector VM(s) through vCenter to clear the cache.

Steps as below:

1. In vCenter, search for the VCF Operations for Networks Collector VM(s) in question
2. Right click each VCF Operations for Networks Collector VM and Navigate to Power > Restart Guest OS

After a period of at least two hours following the reboot(s), you should no longer see the alert.