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

vCenter error: "All required agent virtual machines are not currently deployed on host hostname" (2151502)

  • 0 Ratings

Symptoms

  • Unable to power on or vMotion virtual machines, you see an error similar to:
     All required agent virtual machines are not currently deployed on host hostname.

  • Guest introspection virtual machines (USVMs) are powered off.
    Note: The issue may happen with the virtual machines powered on state.

  • Removing GI is not deleting the USVMs from the Hosts.

  • The EAM/MOB is not accessible.

  • In the EAM logs, you see the errors similar to:

    2017-06-29T12:58:13.407Z | ERROR | eam-0 | VcListener.java | 116 | An unexpected error in the changes polling loop
    java.lang.RuntimeException: Config not saved
         at com.vmware.eam.AgencyImpl.loadConfiguration(AgencyImpl.java:1832)
         at com.vmware.eam.AgencyImpl.loadFromDatabase(AgencyImpl.java:1780)
         at com.vmware.eam.AgencyImpl.<init>(AgencyImpl.java:407)
         at com.vmware.eam.EsxAgentManagerImpl.loadFromDatabase(EsxAgentManagerImpl.java:671)
         at com.vmware.eam.EsxAgentManagerImpl.runPostConfiguration(EsxAgentManagerImpl.java:299)
         at com.vmware.eam.EsxAgentManagerImpl.vCenterConnectionStatusChanged(EsxAgentManagerImpl.java:609)
         at com.vmware.eam.vc.VcListener.main(VcListener.java:135)
         at com.vmware.eam.vc.VcListener.call(VcListener.java:111)
         at com.vmware.eam.vc.VcListener.call(VcListener.java:60)
         at com.vmware.eam.async.impl.AuditedJob.call(AuditedJob.java:35)
         at com.vmware.eam.async.impl.FutureRunnable.run(FutureRunnable.java:52)
         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source

    2017-06-29T12:58:13.427Z |  INFO | eam-0 | VcListener.java | 117 | Full stack trace: java.lang.RuntimeException: Config not saved
     at com.vmware.eam.AgencyImpl.loadConfiguration(AgencyImpl.java:1832)
     at com.vmware.eam.AgencyImpl.loadFromDatabase(AgencyImpl.java:1780)
     at com.vmware.eam.AgencyImpl.<init>(AgencyImpl.java:407)
     at com.vmware.eam.EsxAgentManagerImpl.loadFromDatabase(EsxAgentManagerImpl.java:671)
     at com.vmware.eam.EsxAgentManagerImpl.runPostConfiguration(EsxAgentManagerImpl.java:299)
     at com.vmware.eam.EsxAgentManagerImpl.vCenterConnectionStatusChanged(EsxAgentManagerImpl.java:609)
     at com.vmware.eam.vc.VcListener.main(VcListener.java:135)
     at com.vmware.eam.vc.VcListener.call(VcListener.java:111)
     at com.vmware.eam.vc.VcListener.call(VcListener.java:60)
     at com.vmware.eam.async.impl.AuditedJob.call(AuditedJob.java:35)
     at com.vmware.eam.async.impl.FutureRunnable.run(FutureRunnable.java:52)
     at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)


  • In the EAM wrapper logs, you see entries similar to:

    STATUS | wrapper  | 2017/06/29 12:58:07 | --> Wrapper Started as Daemon
    INFO   | jvm 1    | 2017/06/29 13:31:52 | Exception in thread "vlsi" java.lang.IllegalStateException: Connection pool shut down



  • The EAM status in the vSphere web client is alarmed.

  • Restarting the EAM service does not solve the issue.

Cause

This issue occurs when the EAM service is in a stuck state.

Resolution

To resolve this issue,  clean up the EAM database.
 
To clean up the EAM database, file a support request with VMware Support and quote this Knowledge Base article ID (2151502) in the problem description. For more information, see How to Submit a Support Request.

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: