Cannot configure HA after disabling the Host Welcome login page on an ESXi host

Products

• VMware

Issue/Introduction

Symptoms:

• After disabling the ESX host's Welcome login Web page, the vCenter Server Fault Domain Manager (FDM) agent fails to install with the error:
  
  Unknown installer error.
  
  
• ESXi host has / disabled by running the command:
  
  vim-cmd proxysvc/remove_service "/" httpsWithRedirect
  
  
• You are unable to install the vCenter Server agent service
• In the /var/log/hostd.log file, you see entries similar to:
  
  2011-11-10T15:23:00.527Z [FFA5AA90 verbose 'Proxysvc Req00868'] New proxy client SSL(TCP(local=xxx.xxx.xx.xx:443, peer=192.168.19.30:63940)) 2011-11-10T15:23:00.528Z [4F4B5B90 info 'Proxysvc Req00868'] URL namespace /fdmService.xml does not match any server namespace 2011-11-10T15:23:00.532Z [FFFC2B90 verbose 'Default' opID=C0BD361A-0000028B-61] CloseSession called for session id=5216198a-87ae-9cc0-1f82-63cf9ab6e065 2011-11-10T15:23:00.533Z [FFFC2B90 info 'ha-eventmgr' opID=C0BD361A-0000028B-61] Event 189 : User vpxuser logged out
  2012-02-10T22:31:20.550Z [3B940B90 verbose 'Proxysvc Req00637'] New proxy client SSL(TCP(local=vCenter:443, peer=host:52674))
  2012-02-10T22:31:20.552Z [FFC25A90 warning 'Proxysvc Req00637'] Connection to localhost:9089 failed with error N7Vmacore15SystemExceptionE(Connection refused).
  
  
• When enabling HA, the vpxd logs show errors similar to:
  
  2012-02-10T17:31:14.630-05:00 [34188 warning 'Default'] Closing Response processing in unexpected state: 3
  2012-02-10T17:31:14.630-05:00 [34188 error 'Default'] [FdmClientAdapter] Unexpected error logging into host hostname: Invalid response code: 503 Service Unavailable
  2012-02-10T17:31:14.630-05:00 [34188 error 'Default'] [VpxdClientAdapter] Login to host hostname failed, queuing host sync
  2012-02-10T17:31:14.630-05:00 [34188 info 'vmomi.soapStub[397]'] Resetting stub adapter for server TCP:hostname:443 : Closed
  2012-02-10T17:31:14.631-05:00 [34188 warning 'Default'] [FdmClientAdapter] Got vmacore exception when invoking csi.FdmService.retrieveClusterInfo on hostname: Invalid response code: 503 Service Unavailable
  2012-02-10T17:31:14.631-05:00 [34188 error 'DAS'] [FdmManager::ScanForMaster] Failed to get cluster info from hostname (cluster=ClusterName): class Vmomi::Fault::HostCommunication::Exception(vmodl.fault.HostCommunication)
  
  
• These HA errors may be reported in vCenter Server after disabling the ESX host's Welcome login Web page :
  
  
  • Cluster error – vCenter Server is unable to find a master vSphere HA agent in cluster Cluster in DR
  • Host error – vSphere HA agent for this host has an error: vSphere HA agent cannot be correctly installed or configure
  • Host event error – Cannot upgrade vCenter agent. Unknown installer error
    
    
• The vCenter Server Fault Domain Manager (FDM) may encounter this issue after upgrading from vCenter Server 4.x
  to vCenter Server 5.0

Cause

Resolution

This issue is resolved in VMware vCenter Server 5.0 Update 2, available at VMware Downloads. For more information, see the Resolved Issues section of the VMware vCenter Server 5.0 Update 2 Release Notes.

To work around this issue when you are unable to upgrade, re-enable the Host Welcome login page.

To re-enable the Host Welcome login page:

1. Connect to the ESX host directly via remote KVM or an SSH session.
2. Run this command:
   
   vim-cmd proxysvc/add_tcp_service "/" httpsWithRedirect localhost 8309

Additional Information

vSphere HA (FDM) agent fails to install on an ESXi host when network traffic throughput between ESXi and vCenter Server is insufficient
ESXi ホスト上でホストの [ようこそ] ログイン ページを無効化した後、HA を構成できなくなる