"Source ESX Agent Manager is not responsive" error during migration assistance at precheck phase

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Running Prechecks reported the following errors: Error: Source ESX Agent Manager is not responsive!
• Checking the service-status EAM showed running.
• You will see similar error message in CollectRequirements_com.vmware.eam_xx.log file as mentioned below:

CollectRequirements_com.vmware.eam_xx.log
20-02-18T15:50:35.106Z INFO eam EsxAgentManager service already started and running.
2020-02-18T15:50:35.107Z INFO vc_connector Parse rhttpproxy config file E:\Busdata\VMware\vCenterServer\vCenterServer\cfg\vmware-rhttpproxy\config.xml
2020-02-18T15:50:35.107Z INFO vc_connector Proxy http port is configured to: 80
2020-02-18T15:50:35.108Z INFO vc_connector Proxy https port is configured to: 443
2020-02-18T15:50:35.108Z INFO eam Going to access: http://localhost:80/eam/imx/esx_vm_16x.png
2020-02-18T15:50:37.121Z WARNING eam vmware-eam service is not fully started, waiting till get up and running. Sleeping for5seconds. Error: HTTP Error 503: Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:0000000001D800D0] _serverNamespace = /eam _isRedirect = false _port = 15005)

wrapper.log
STATUS | wrapper  | 2020/02/19 09:08:42 | JVM appears hung: Timed out waiting for signal from JVM.  Restarting JVM.
ERROR  | wrapper  | 2020/02/19 09:09:47 | Shutdown failed: Timed out waiting for signal from JVM.
STATUS | wrapper  | 2020/02/19 09:09:47 | Dumping JVM state.
ERROR  | wrapper  | 2020/02/19 09:09:51 | JVM did not exit on request, termination requested.
 

Environment

VMware vCenter Server 6.0.x
VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.7.x
VMware vCenter Server Appliance 6.0.x
VMware vCenter Server 6.7.x
VMware vCenter Server Appliance 6.5.x

Cause

JVM Crashed

Resolution

To resolve this issue, please follow the below steps:

1. Navigate to the service-layout.mfx file in the below location
   • Location: C:\ProgramData\VMware\vCenterServer\cfg\service-layout.mfx (Path can be different)
2. Check the eam_firstboot entry for StacksizeKB the data is available, if its missing then proceed further.
3. You need to add the missing value which is 256 for StacksizeKB entry.

Before Changes:

#firstboot_name	cloudvm_name	ciswin_name	customMB	tinyMB	largeMB	MaxPermMB	StacksizeKB	tinyGCThreads	largeGCThreads
eam_firstboot	vmware-eam	EsxAgentManager	0	96	512	256		1	2

After Changes:

#firstboot_name	cloudvm_name	ciswin_name	customMB	tinyMB	largeMB	MaxPermMB	StacksizeKB	tinyGCThreads	largeGCThreads
eam_firstboot	vmware-eam	EsxAgentManager	0	96	512	256	256	1	2

4. Retry the Migration process.