View Connection Server cannot communicate with View Agent on a Linux virtual machine.

Problem

In View Administrator, the Linux virtual machine is displayed as Agent Unreachable. This problem occurs after View Agent was installed and the View Agent service started successfully on the Linux machine.

Cause

One cause might be that the Linux machine cannot resolve the FQDNs of the View Connection Server instances.

After installation, View Agent stores a list of FQDNs of the View Connection Server instances in the /etc/vmware/viewagent-machine.cfg configuration file. View Agent uses FQDNs even if you specify an IP address of a View Connection Server instance with the -b parameter during the View Agent installation.

A second cause might be that the hostname of the Linux machine itself cannot be resolved.

Procedure

  1. On the Linux machine, open the View Agent log file.

    /usr/lib/vmware/viewagent/viewagent-debug.log

  2. Look for messages that indicate the hostname of the View Connection Server instance cannot be resolved.

    For example:

    2015-01-31T09:21:33.516Z DEBUG <JMS Handler for:svohraUb12x6> [JmsManager] 
         Using connection broker sm-15q1-broker.myDomain.com 
    2015-01-31T09:21:33.518Z DEBUG <JMS Handler for:svohraUb12x6> [JmsManager] 
         Unable to resolve hostname for sm-15q1-broker.myDomain.com
    
  3. Make sure the DNS service is configured properly on the Linux machine.

    The steps for configuring DNS vary depending on the Linux distribution and release. For instructions, consult the documentation for your Linux distribution.

    As a workaround, you can manually add the View Connection Server FQDNs to the /etc/hosts file on the Linux machine. However, this method is not recommended for production use. The proper solution is to configure the DNS service so that the Linux machine can resolve the View Connection Server FQDNs.

    After you take these steps, ping the View Connection Server hostnames to verify that they can be resolved. For example:

     ping sm-15q1-broker.myDomain.com

  4. If the problem continues, make sure that the system hostname of the Linux machine is resolvable.

    For example, on CentOS you might take the following steps:

    1. Open a terminal window and run the hostname command.

      The machine's hostname is displayed.

    2. Open the etc/hosts file and add the hostname.
      su
      nano /etc/hosts 
      # Add the hostname:
      127.0.0.1 <your hostname> 
      
    3. Ping the hostname to verify that it can be resolved.
      ping <your hostname>

Results

Note:

If you specify the DNS server on the Linux machine by manually editing the /etc/resolv.conf file, the setting might become lost in some Linux distributions. The setting is preserved if you specify the DNS server in the /etc/hosts file. For complete instructions for configuring DNS and the hostname, consult the documentation for your Linux distribution and release.