Knowledge Base

Verifying that the agent is running and responding

1. Log in to the ESX service console.
2. Verify that the agent is running by running one of these commands:
   
   ps aux | grep lm-agent
   
   service lm-agent status
   
   
   If the agent is running, the last command returns the message:
   
   lm-agent (pid <###>) is running...
   
   
   • If the agent is not running, run the command:
     
     service lm-agent start
     
     
   • If the agent is running but seems unresponsive, try restarting the agent service. Run the command:
     
     service lm-agent restart
     
     
     Note: For more information, see Lab Manager Agent service command options (1005342).
     
     
3. If the agent does not start:
   
   1. Verify that the server's disk is not out of space. Run the command:
      
      df -h
      
      
   2. Restart the ESX host. Verify that the agent is running after the ESX host restarts.
   3. If the problem persists, enable verbose debug logging, collect the agent logs, and contact VMware Technical Support.
      
      
      1. To enable debug logging, see Enabling Verbose (Debug) Logging in Lab Manager 2.x (1000002) or Enabling Verbose (Debug) Logging in Lab Manager 3.x (1006776).
      2. Gather these files:
         
      • /var/log/labmanager/agentinfo.log
      • /var/log/labmanager/lm-agent-mono.log
      • /var/log/labmanager/lm-agent-mono-watch.log
        
        
4. Verify that the agent is accessible over the network, from a different server:
   
   
   1. Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
   2. Run the telnet <esx_hostname> 5212 command.
   3. If the command fails with a network connection error, verify that the server is reachable with ping, and that there are no firewalls blocking the connection.

Checking the Lab Manager Agent installed version

1. Log in to the ESX service console.
2. Run the command:
   
   rpm -qa | grep labmanager
   
   The versions are listed.