将 vCenter Server 6.0 迁移到 6.5 时出现错误“导出 vSphere ESX Agent Manager 时出现内部错误 (Internal error occurs during Export of vSphere ESX Agent Manager)”

Products

• VMware vCenter Server

Issue/Introduction

本文介绍在将 vCenter Server 6.0（Windows 版本）迁移到 vCenter Server Appliance 6.5 期间如何从 EAM 导出故障中恢复。

Symptoms:
免责声明：本文是 "Internal error occurs during Export of vSphere ESX Agent Manager" error when migrating vCenter Server 6.0 to 6.5 (2147898) 的翻译版本。尽管我们会不断努力为本文提供最佳翻译版本，但本地化的内容可能会过时。有关最新内容，请参见英文版本。

---

• 将安装在 Windows 上的 vCenter Server 6.0 迁移到 vCenter Server Appliance 6.5 失败并显示以下错误︰
  
  Internal error occurs during Export of vSphere ESX Agent Manager

源 Windows vCenter Server 上的 vCenter Server 6.x 升级失败后会在桌面上创建一个名为VMware-VCS-logs-<year><month><day><hour><minute><second>.zip的文件。在此 zip 文件中会找到以下日志条目。有关详细信息，请参见 Triaging a vCenter Server 6.0 installation or upgrade failure (2105258)。

• 在UpgradeRunner.log中会发现以下错误消息︰
  
  2016-11-16T14:49:53.634Z ERROR upgrade.states.component_states eam:Export: Remote script failed with an error [InternalError()]
  2016-11-16T14:49:53.634Z ERROR upgrade.states.component_states eam:Export: failed with internal error. For details take a look at Export_com.vmware.eam_2016_11_16_09_42.log.
  2016-11-16T14:49:53.638Z WARNING wf.wf_processor State Export com.vmware.eam has failed.

注意：UpgradeRunner.log 位于 VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade 文件夹。

Environment

VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.5.x

Resolution

EAM 导出失败的原因有多种。验证以下解决方案以解决此问题。

JVM 堆问题

症状

• 在 Export_com.vmware.eam.log 中发现以下错误消息︰
  
  2016-11-16T14:49:47.786Z 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:0000000001F40F00] _serverNamespace = /eam _isRedirect = false _port = 15005)
  2016-11-16T14:49:52.786Z ERROR __main__ Upgrade Phase 'eam:Export' failed. Exception: expected string or buffer
  
  注意：Export_com.vmware.eam.log位于VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade文件夹中。
  
  
• 在 eam.log 中发现以下错误消息︰
  
  2016-11-14T02:29:10.868-05:00 | INFO | eam-0 | VcConnection.java | 167 | Connecting to vCenter as com.vmware.vim.eam extension
  2016-11-14T02:29:10.881-05:00 | INFO | eam-0 | VcConnection.java | 603 | Connecting to https://vCenter:8089/sdk/vimService via vCenter proxy http://localhost:80
  2016-11-14T02:29:15.900-05:00 | ERROR | eam-0 | VcConnection.java | 179 | Failed to login to vCenter as extension. vCenter has probably not loaded the EAM extension.xml yet.: Cannot complete login due to an incorrect user name or password.
  2016-11-14T02:29:15.900-05:00 | WARN | eam-0 | VcListener.java | 114 | Trying to recover from error
  
  
• 在 wrapper.log 中发现以下消息︰
  
  INFO | jvm 2 | 2016/11/16 04:24:12 | java.lang.OutOfMemoryError: Java heap space
  
  注意：eam.log 和 wrapper.log 位于 VMware-VCS-logs-<year><month><day><hour><minute><second>/vcs_logs/eam 文件夹中。

解决方案

该问题在 VMware vCenter Server 6.5 b（可从 VMware Downloads 获取）中已解决。

要临时解决此问题，请在 vCenter Server 6.0（Windows 版本）上启动 VMware ESX Agent Manager (EsxAgentManager) 服务，并再次运行迁移。有关重新启动服务的详细信息，请参见 Stopping, starting, or restarting VMware vCenter Server 6.x services (2109881)。

端口配置

症状

• 在 UpgradeRunner.log 中找到以下错误消息︰
  
  2016-11-16T20:33:32.342Z ERROR __main__ Cannot perform the upgrade, because of the following not allowed custom ports: HTTP Port (81, default 80)
  
  注意：UpgradeRunner.log位于VMware-VCS-logs-<year><month><day><hour><minute><second>/vcsUpgrade文件夹中。
  
  
• EAM 服务使用的是自定义端口。在上述示例中，默认端口 80 已更改为 81。

解决方案

要解决此问题，请在此文件中将 EAM 端口更改回默认端口 (80)：eam.properties.

注意：eam.properties 文件的默认位置为 C:\Program Files\VMware\Infrastructure\tomcat\webapps\eam\WEB-INF。

Additional Information

"Internal error occurs during Export of vSphere ESX Agent Manager" error when migrating vCenter Server 6.0 to 6.5