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

  • Esxi host fails to update information to vCenter Server
  • On the Summary page of the host, the following errors may appear:
    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 ESXi logs /var/log/vpxa.log may contain entries similar to: 

    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'App' opID=task-internal-349047-7f8a0b5a] [VpxVmomi] Invoke error: vpxapi.VpxaService.login session: Throw: vim.fault.InvalidLogin
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=task-internal-] User agent is 'VMware-client/4.1.0'
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=task-internal-] HTTP Response: Client: NeedsContentLength: false Under standsChunking: true CanKeepAlive: true (PresetContentLength -1)
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 verbose 'SoapAdapter.HTTPService' opID=task-internal-] HTTP Response: Complete (processed 585 bytes)
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 info 'App' opID=task-internal-] [VpxLRO] -- FINISH task-internal-349047 -- -- vpxapi.VpxaService.login -- 52 
    [YYYY-MM-DDTHH:MM:SS] F6E73B90 info 'App' opID=task-internal-] [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: "x.x.x.x"
    [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)'

  • On vCenter server /var/log/vmware/vpxd/vpxd-xxx/log file contains similar error.

    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
    --> )
  • hostd.log on issue host var/run/log/hostd.log file may contain similar error

     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 datastore might fail with an error "An error occurred while communicating with the remote host" and the Files tab remain empty. 

Environment

VMware ESXi 8.x
VMware ESXi 7.x

Cause

  • The issue occurs when the vpxuser password is out of sync with the vCenter Server database and the password on the host or the password is manually modified.
  • The vpxuser account is created by vCenter Server when adding an ESX host.
  • 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 needs to be reconfigured.
 
To resynchronize the password with the vCenter Server database:
  1. Right-click the ESXi host and click Disconnect.
  2. Reconnect the host and enter the root password when prompted.
    1. How to Disconnect Your Managed ESXi Host
      1. Use the vSphere Client to disconnect a managed host from vCenter Server.
      2. Navigate to Home > Hosts and Clusters and select a host.
      3. Right-click the host and select Connection > Disconnect from the pop-up menu.
      4. In the confirmation dialog box that appears, click Ok.
      5. 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. How to Reconnect Your Managed ESXi Host
      1. Use the vSphere Client to reconnect a managed host to a vCenter Server system.
      2. Navigate to Home > Hosts and Clusters and select a host.
      3. Right-click the host and select Connection > Connect from the pop-up menu.
      4. 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
When reconnected, the virtual machines are placed in a folder in VMs and Templates view and appear in the Hosts and Clusters view under the hosts they are registered to. Reorganize virtual machines into their correct folders.

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

Additional Information

Powered by Wolken Software