Remote Collector fails to stay connected in vRealize Operations Manager 6.2.x

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• Multiple remote collectors goes into Collector Down state and were unable to come back online in vRealize Operations Manager UI.
• You observe that few adapter instaces in remote collector takes more than 5 mins to collect the data.
• In the logs\adapters\VMwareAdapter\VMwareAdapter_62524.log file, you see the entries similar to:
  
  2016-12-10 09:28:21,895 INFO [Collector worker thread 10] (62524) com.integrien.alive.common.adapter3.AdapterBase.collectBase - End collection, took 381 seconds.
  
  
• In the /data/vcops/log/collector.log file, you see entries similar to:
  
  [warning 2016/12/10 09:27:19.398 CET vRealize Ops Collector-9a76d719-cee8-####-####-########014 <poolTimer-CollectorTovRealize Ops Controller-dd7a1381-e794-####-####-########71e2Pool-vRealize Ops Controller-dd7a1381-e794-####-####-########1e2-[157.96.177.13:6061]-17474> tid=0x3ad74] Pool unexpected closed socket on server connection=SubscriptionConnectionImpl[157.96.177.21:10000:closed]). Server unreachable: could not connect after 1 attempts
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs due to ping loss when vRealize Operations Manager collector node pings controller to check the heartbeat of the controller node.

Resolution

To resolve this issue, use these options:

• Increase the collection interval of the adapter instances.
• Check the latency between Remote collector and analytics node ( should be less than 200ms).
• Correct ping latency and intermittent network communication problems.