Symptoms: -Below error is seen while powering on a VM from Vcenter : "vim.fault.InsufficientAgentVmsDeployed" -Service redeployment in the NSX-T manager would show up as in progress
LOGS TO LOOK FOR AND ITS LOCATION : /var/log/proton/proton-tomcat-wrapper.log.1
INFO | jvm 1 | 2022/08/08 08:16:18 | "EamPollingThread" #1314 daemon prio=5 os_prio=0 tid=0x0000006621d37800 nid=0x3a50 runnable [0x000003a4ebf01000] INFO | jvm 1 | 2022/08/08 08:16:18 | java.lang.Thread.State: RUNNABLE INFO | jvm 1 | 2022/08/08 08:16:18 | at java.net.SocketInputStream.socketRead0(Native Method)
Environment
VMware NSX-T Data Center
Cause
The EamPollingThread is getting stuck indefinitely while waiting for a response
Resolution
This issue is resolved in NSX-T 3.1.0 and higher.
Workaround: Restart proton service in the NSX-T manager cli: /etc/init.d/proton restart
To check the status of the service after restart: /etc/init.d/proton status
Additional Information
Impact/Risks: Customer is unable to power on any vm's on the affected host and the guest introspection service vm (GI SVM) is not available after a redeployment of the vm. The status in the NSX-T manager stays at "in-progress."