End Point Operations Agent is not collecting data in vRealize Operations Manager 6.2.0a or 6.2.1

Products

• VMware

Issue/Introduction

Symptoms:

• The End Point Operations Agent is not collecting any data after upgrading to VMware vRealize Operations Manager 6.2.0 / 6.2.
• End Point Operations Agent successfully register with VMware vRealize Operations Manager.
• In the C:\ep-agent\log\agent.log(Windows) or /opt/vmware/epops-agent/log/agent.log(Linux) file of the target machine, you see entries similar to:
  

  
  ERROR [pool-3-thread-1] [ResourceRepositoryService] The following property is missing for platform resource: platform.type

ERROR [pool-3-thread-1] [ConfigurationCommandsService] Exception during configuration and scheduling

org.hyperic.hq.configuration.agent.repository.ResourceRepositoryException: Configuration info is missing must-have resource properties

at org.hyperic.hq.configuration.agent.repository.ResourceRepositoryService.filterPlatformProperties(ResourceRepositoryService.java:291)

at org.hyperic.hq.configuration.agent.repository.ResourceRepositoryService.getFilteredResourceProperties

(ResourceRepositoryService.java:272)

at org.hyperic.hq.configuration.agent.repository.ResourceRepositoryService.getResourceAndAncestorsConfigurationAndProperties

(ResourceRepositoryService.java:220)

at org.hyperic.hq.configuration.agent.repository.ResourceRepositoryService.getResourceAndAncestorsConfiguration

(ResourceRepositoryService.java:194)

at org.hyperic.hq.configuration.agent.server.ConfigurationCommandsService.buildPushRuntimeDiscoveryConfigArgs

(ConfigurationCommandsService.java:217)

at org.hyperic.hq.configuration.agent.server.ConfigurationCommandsService.handlePushRuntimeDiscoveryConfig

(ConfigurationCommandsService.java:160)

at org.hyperic.hq.configuration.agent.server.ConfigurationCommandsService.configurationAndScheduling

(ConfigurationCommandsService.java:94)

at org.hyperic.hq.configuration.agent.server.ConfigurationCommandsService.configure(ConfigurationCommandsService.java:82)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)

at org.hyperic.hq.transport.PollerClientImpl$PollingRunnable$1.run(PollerClientImpl.java:138)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Cause

This issue occurs when vRealize Operations Manager is unable to reach End Point Operations Agent after the End Point Operations Agent registration with vRealize Operations Manager, but before the metric collection begins.

Resolution

This is a known issue with the End Point Operations Agent affecting vRealize Operations Manager 6.2.0a and 6.2.1.

This issue is resolved in vRealize Operations Manager 6.3, available at VMware Downloads.

To work around this issue, if you do not want to upgrade to 6.3, apply the hotfix:

1. Download the zip file attached to this article:
   
   6.2.0a - 2145357_epops_620.zip
   6.2.1 - 2145357_epops_621.zip
   
   
2. Stop the End Point Operations Agent.
   Linux:
   
   service epops-agent stop or
   /opt/vmware/epops-agent/bin/ep-agent.sh stop
   
   Windows:
   \ep-agent\bin\ep-agent.bat stop
   
   
3. Delete data and logs directory in the agent installation location:
   Linux:
   
   /opt/vmware/epops-agent/data
   /opt/vmware/epops-agent/log
   
   Windows:
   
   c:\ep-agent\data
   c:\ep-agent\log
   
   
4. Delete the file epops-token:
   
   Windows location - C:\ProgramData\VMware\EP Ops Agent
   Linux location - /etc/epops/
   
   
5. Extract the JAR from the applicable ZIP file.
   
   6.2.0a - dcs-agent-handler-configuration-6.2.0.jar
   6.2.1 - dcs-agent-handler-configuration-6.2.1.jar
   
   
6. Replace the dcs-agent-handler-configuration-XXX.jar file in the agent installation location under the directory bundles\agent-x86-64-win-6.2.0\lib\handlers with the extracted JAR file.
7. Start the End Point Operations Agent and configure if necessary:
   Linux:
   service epops-agent start or
   /opt/vmware/epops-agent/bin/ep-agent.sh start
   
   Windows:
   \ep-agent\bin\ep-agent.bat start