Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Virtualization Manager (VMAN) > vCenter not polling due to DNS resolution failure

vCenter not polling due to DNS resolution failure

Updated June 20, 2017

Overview

Virtualization Manager does not poll vCenter servers and the following event can be seen in the master.log file located in /var/log/hyper9/:

 

2514-05-11 01:21:23,715 [ViSdkExecutor-7228] ERROR com.hyper9.data_collection.visdk.jobs.EnumerateEnvironmentJob:155 - Failed to connect to vCenter001.SolarWinds.local
java.net.UnknownHostException: vCenter001.SolarWinds.local: Name or service not known
    at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) ~[na:1.8.0_121]
    at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928) ~[na:1.8.0_121]
    at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) ~[na:1.8.0_121]
    at java.net.InetAddress.getAllByName0(InetAddress.java:1276) ~[na:1.8.0_121]
    at java.net.InetAddress.getAllByName(InetAddress.java:1192) ~[na:1.8.0_121]
    at java.net.InetAddress.getAllByName(InetAddress.java:1126) ~[na:1.8.0_121]
    at java.net.InetAddress.getByName(InetAddress.java:1076) ~[na:1.8.0_121]
    at com.hyper9.data_collection.visdk.jobs.BaseJob.isReachableHost(BaseJob.java:725) ~[vi-sdk-executor-7.1.0-SNAPSHOT.jar:na]
    ... 7 common frames omitted
Wrapped by: com.hyper9.library.vmware.exception.UnreachableDataSourceException: Connection Failure. vCenter001.SolarWinds.local unreachable on port 443

Environment

All VMAN versions

Cause 

The DNS server is incorrectly resolving the vCenter server.

Resolution

Perform any of the following options:

  • Correct the DNS information on the DNS server.
  • Change the polling details of the vCenter server in VMAN to poll by IP address:
    1. Log in to the Virtualization Manager Web Console.
    2. Go to Setup > Data Sources.
    3. Select the vCenter server and click Edit.
    4. Enter the IP address details and save the changes.
    5. Retry polling and verify that the issue has been resolved.
 

 

Last modified
18:16, 20 Jun 2017

Tags

Classifications

Public