Host Summary page reports "Cannot synchronize host" or "Quick stats on <Hostname> is not up-to-date"
search cancel

Host Summary page reports "Cannot synchronize host" or "Quick stats on <Hostname> is not up-to-date"

book

Article ID: 368262

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere ESXi

Issue/Introduction

  • Information about an ESXi host fails to update in vCenter Server
  • The following errors may be observed in the summary page of the host in vCenter:
    VMware esx cannot synchronize host "incorrect username and password"
    Cannot synchronize host : Cannot complete login due to an incorrect user name or password
    Quick stats on "Hostname" is not up-to-date
  • In the /var/log/vmware/vpxd/vpxd-###/log file of the vCenter, the following errors may be observed:

    YYYY-MM-DDTHH:MM:SS error vpxd[#####] [Originator@6876 sub=Vmomi opID=########] [VpxaClientAdapter] Last login to ###################. failed; timeout; no host sync yet
    YYYY-MM-DDTHH:MM:SS error vpxd[#####] [Originator@6876 sub=Vmomi opID=########] Cannot contact the specified host (###################)
    YYYY-MM-DDTHH:MM:SS info vpxd[#####] [Originator@6876 sub=vmomi.soapStub[7384] opID=CdrsLoadBalancer-########] SOAP request returned HTTP failure; <<io_obj p:0x00007fe054108338, h:19, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-###/sdk>, method: login; code: 500(Internal Server Error); fault: (vim.fault.InvalidLogin) {
    -->    faultCause = (vmodl.MethodFault) null,
    -->    faultMessage = <unset>
    -->    msg = "Received SOAP response fault from [<<io_obj p:0x00007fe054108338, h:19, <UNIX ''>, <UNIX '/var/run/envoy-hgw/hgw-pipe'>>, /hgw/host-###/sdk>]: login
    --> Cannot complete login due to an incorrect user name or password."
    --> }
    YYYY-MM-DDTHH:MM:SS error vpxd[#####] [Originator@#### sub=Vmomi opID=CdrsLoadBalancer-#######] Failed to login on host; <</hgw/host-###>, /sdk>, N3Vim5Fault12InvalidLogin9ExceptionE(Fault cause: vim.fault.InvalidLogin

  • In the /var/log/vpxa.log file of the problematic ESXi host, the following entries may be observed:

    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'App' opID=########] [VpxVmomi] Invoke error: vpxapi.VpxaService.login session: Throw: vim.fault.InvalidLogin
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=########] User agent is 'VMware-client/4.1.0'
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=########] HTTP Response: Client: NeedsContentLength: false Under standsChunking: true CanKeepAlive: true (PresetContentLength -1)
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=########] HTTP Response: Complete (processed 585 bytes)
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 info 'App' opID=########] [VpxLRO] -- FINISH task-internal-349047 -- -- vpxapi.VpxaService.login -- 52 
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 info 'App' opID=########] [VpxLRO] -- ERROR task-internal-349047 -- -- vpxapi.VpxaService.login: vim.f ault.InvalidLogin: Result: (vim.fault.InvalidLogin) { dynamicType = , faultCause = (vmodl.MethodFault) null,
    msg = "Cannot complete login due to an incorrect user name or password.", } Args: Arg userName: "vpxuser" Arg password: (not shown) Arg soapPort: 443 Arg hostIp: "#.#.#.#"
    [YYYY-MM-DDTHH:MM:SS] F6DF1B90 verbose 'App'] CloseSession called for session id
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService'] User agent is 'VMware-client/4.1.0' [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService'] HTTP Response: Client: NeedsContentLength: false UnderstandsChunking: true CanKeepAlive: true (PresetContentLength -1)'

  • In the var/run/log/hostd.log file of the problematic host, the following entries are observed:

YYYY-MM-DDTHH:MM:SS info hostd [Originator@6876 sub=Vimsvc.ha-eventmgr opID=HostSync-########] Event 5071 : Cannot login [email protected]
YYYY-MM-DDTHH:MM:SS info hostd [Originator@6876 sub=Solo.Vmomi opID=HostSync-########] Activation finished; <<########, <TCP '127.0.0.1 :8307'>, '127.0.0.1 : 48220'>>, ha-sessionmgr, vim.SessionManager.login>
YYYY-MM-DDTHH:MM:SS verbose hostd [Originator@6876 sub=Solo.Vmomi opID=HostSync-########] Arg userName:--> "vpxuser"
YYYY-MM-DDTHH:MM:SS verbose hostd [Originator@6876 sub=Solo.Vmomi opID=HostSync-########] Arg password: --> (not shown)-->
YYYY-MM-DDTHH:MM:SS verbose hostd [Originator@6876 sub=Solo.Vmomi opID=HostSync-########] Arg locale:--> ""
YYYY-MM-DDTHH:MM:SS info hostd [Originator@6876 sub=Solo.Vmomi opID=HostSync-########] Throw vim. fault. PasswordExpired
YYYY-MM-DDTHH:MM:SS info hostd [Originator@6876 sub=Solo. Vmomi opID=HostSync-########] Result: 
-- >(vim. fault. PasswordExpired)
->   {msg ='',

  • Browsing files in the datastore might fail with the error "An error occurred while communicating with the remote host" and the files tab remains empty. 

Environment

  • VMware ESXi 8.0
  • VMware ESXi 7.0

Cause

  • The issue occurs when the vpxuser password is out of sync with the vCenter Server database and the password on the host or when the password is manually modified.
  • The vpxuser account is created by vCenter Server when adding an ESX host to vCenter.
  • VMware does not recommend modifying the vpxuser account

Resolution

To resolve this issue, resynchronize the password with the vCenter Server database.
 
Note: Do not remove the host from the Inventory. When an ESX/ESXi host is removed from the vCenter Server Inventory, virtual machines are removed from their respective folders, performance data for the host is lost, and any Distributed Virtual Switch configurations on the host will need to be reconfigured.
 
To resynchronize the password with the vCenter Server database:
  1. Disconnect the ESXi host from vCenter's inventory
    1. From the vCenter UI, navigate to Home > Hosts and Clusters and select a host.
    2. Right-click the host and select Connection > Disconnect from the pop-up menu.
    3. In the confirmation dialog box that appears, click Ok.
    4. If the managed host is disconnected, the word “disconnected” is appended to the object name in parentheses, and the object is dimmed. All associated virtual machines are similarly dimmed and labeled.
  2. Reconnect the host and enter the root password when prompted.
    1. From the vCenter UI, navigate to Home > Hosts and Clusters and select a host.
    2. Right-click the host and select Connection > Connect from the pop-up menu.
    3. When the managed host’s connection status to vCenter Server is changed, the statuses of the virtual machines on that managed host are updated to reflect the change

After the host is successfully reconnected to vCenter Server, its associated virtual machines are automatically restored. In the VMs and Templates view, these VMs are placed into a default folder, which may not reflect their original organizational structure. Simultaneously, in the Hosts and Clusters view, the virtual machines reappear under the host to which they are registered.

To maintain consistency and ensure proper management, it's recommended to manually reorganize the virtual machines into their intended folders within the VMs and Templates view. This helps preserve logical grouping, simplifies navigation, and aligns with operational standards.

If the issue persists, refer to Reconnecting a host to vCenter Server fails with the error: Rejected password for user vpxuser.

Additional Information

Powered by Wolken Software