Search the VMware Knowledge Base (KB)
View by Article ID

Testing a VMware vSphere adapter instance connection fails in vRealize Operations Manager 6.x (2149144)

  • 0 Ratings

Symptoms

When the vCenter address is entered by short name or FQDN in the VMware vSphere adapter configuration, you experience these symptoms:
  • Testing the connection of a VMware vSphere adapter shows the error:

    Unable establish a valid connection to the target system.  Error trying to establish connection

  • Pinging the vCenter server from a vRealize Operations Manager node fails.
  • In the /storage/vcops/log/collector.log file you see entries similar to:

    ERROR [Task Processor worker thread 8]  com.integrien.alive.common.adapter3.AdapterBase.onCheckCertificate - Could not reach host
    java.net.UnknownHostException: [host name]
            at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:184)
            at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
            at java.net.Socket.connect(Socket.java:589)
            at java.net.Socket.connect(Socket.java:538)
            at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
            at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
            at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
            at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:264)
            at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
            at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
            at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1105)
            at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:989)
            at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:987)
            at java.security.AccessController.doPrivileged(Native Method)
            at java.security.AccessController.doPrivilegedWithCombiner(AccessController.java:782)
            at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:986)
            at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)
            at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
            at com.integrien.alive.common.adapter3.AdapterBase.onCheckCertificate(AdapterBase.java:2319)
            at com.integrien.alive.common.adapter3.AdapterBase.checkCertificate(AdapterBase.java:2226)
            at com.integrien.alive.collector.Collector.testConnection(Collector.java:992)
            at com.integrien.alive.collector.CollectorTaskHandler.handleTestConnection(CollectorTaskHandler.java:240)
            at com.integrien.alive.common.communication.task.TaskTest.processTask(TaskTest.java:35)
            at com.integrien.alive.common.communication.CommunicatorWorkItem.run(CommunicatorWorkItem.java:36)
            at com.integrien.alive.common.util.ThreadPool$WorkerItem.run(ThreadPool.java:253)
            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)
    2017-02-20 03:28:30,245 WARN  [Task Processor worker thread 8]  com.integrien.adapter.vmware.VcCollector.shutdown - VcCollector shutting down

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 failed name resolution.

Resolution

To resolve this issue, add vCenter Server to the vRealize Operations Manager's host file or change the Short name /FQDN to the IP Address in the VMware vSphere adapter's configuration.

To add the vCenter Server to the hosts file:
  1. Log in to the master node as root through SSH or Console.
  2. Open the /etc/hosts file using a text editor.
  3. Add a line containing the vCenter Server information.

    For Example: 192.168.1.50 vcenter vcenter.vmware.com

  4. Save and close the file.
  5. Repeat steps 1-4 on all nodes in the cluster.

Additional Information

Adding the vCenter's information to the hosts file on each node keeps the vCenter server collecting in case the adapter instance moves to another node.
 
If the adapter instance was already saved, restart the VMware vSphere adapter instance:  
  1. Log in to the vRealize Operations Manager UI as an administrator user.
  2. Navigate to Administration Solutions.
  3. Select the VMware vSphere solution, then select the adapter instance.
  4. Click Stop, then click Start.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: