Enhanced replication shows Not active and mapping error Fault occurred while performing health check. Details: Login: Login denied. Login request is denied.
Article ID: 390138
Updated On:
Products
Issue/Introduction
Symptoms:
Legacy replication completes successfully without any errors.
Enhanced replication is stuck at not active status.
Reconfiguring replication failed with A replication error occurred at the vSphere Replication Server for replication 'VM_Name'. Details: 'No connection to VR Server for virtual machine VM_Name on host Host_Name in cluster Cluster_Name in Site_Name': Unknown
Enhanced Replication mapping errors:
Fault occurred while performing health check. Details: Login: Login denied. Login request is denied.
/var/run/log/hbrsrv.log shows entries that look similar to:
2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] HbrError stack:2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [0] Invalid argument2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [1] Unverified token with ID '#####-####-####-####-##########'had invalid signature.2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [2] ClientConnection (client=[Source_ESXIhost]:55852) failed login attempt2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [3] Hiding full error from unauthenticated client.2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] HbrError stack:2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [0] Login request is denied.2025-02-21T19:15:37.446Z Er(163) hbrsrv[6594860]: [Originator@6876 sub=Main opID=hsl-0] [1] Converting error to wire failure2025-02-21T19:15:37.446Z In(166) hbrsrv[2099502]: [Originator@6876 sub=Delta] ClientConnection (ClientCnx '[Source_ESXIhost]:55852' id=0 <shut> <uninit>) is stopping ...2025-02-21T19:15:37.446Z In(166) hbrsrv[2099502]: [Originator@6876 sub=Asio] Closing LWD ASIO <UDS '/var/run/vmware/hbrsrv-data-tunnel:27'> -> <Tunneled Secure TCP 'Source_ESXIhost:55852'>2025-02-21T19:15:37.446Z In(166) hbrsrv[2100789]: [Originator@6876 sub=Delta] HbrSrv cleaning out ClientConnection ([Source_ESXIhost]:55852
The hbrsrv reported persistent database errors:
2025-12-29T11:11:07.674Z Wa(164) hbrsrv[2101159]: [Originator@6876 sub=Db groupID=PING-GID-2a####a4-####-####-####-27########f3c opID=3675e7e1-4bf9-4699-9581-eb56776c3cff-HMS-944] Error opening database: SQLite error 14: unable to open database file2025-12-29T11:11:07.674Z In(166) hbrsrv[2101159]: [Originator@6876 sub=Main groupID=PING-GID-2a####a4-####-####-####-27########f3copID=3675e7e1-4bf9-4699-9581-eb56776c3cff-HMS-944] [0] SQLite error 14: unable to open database file2025-12-29T11:11:07.692Z Wa(164) hbrsrv[2101159]: [Originator@6876 sub=Db groupID=PING-GID-2a####a4-####-####-####-27########f3copID=3675e7e1-4bf9-4699-9581-eb56776c3cff-HMS-944] Error opening database: SQLite error 14: unable to open database file2025-12-29T11:11:07.692Z In(166) hbrsrv[2101159]: [Originator@6876 sub=Main groupID=GID-2a####a4-####-####-####-27########f3copID=3675e7e1-4bf9-4699-9581-eb56776c3cff-HMS-944] [0] SQLite error 14: unable to open database file
/var/run/log/hbr-agent.log
2025-06-20T19:07:35.229Z In(166) hbr-agent-bin[2105431]: [0x00000002c2b7e700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##:32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server: (18) Login denied.
2025-06-20T19:07:35.229Z In(166) hbr-agent-bin[2105431]: [0x00000002c2b7e700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##:32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server additional error info: Login request is denied.
2025-06-20T19:07:35.229Z In(166) hbr-agent-bin[2105431]: [0x00000002c2b7e700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##:32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server: (18) Login denied.
2025-06-20T19:07:35.229Z In(166) hbr-agent-bin[2105431]: [0x00000002c2b7e700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##:32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server additional error info: Login request is denied.
2025-06-20T19:07:35.230Z In(166) hbr-agent-bin[2105431]: [0x00000002c2afd700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##:32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server: (18) Login denied.
2025-06-20T19:07:35.230Z In(166) hbr-agent-bin[2105431]: [0x00000002c2afd700] error: [Proxy [Group: PING-GID-##########-####-####-####-###########] -> [##.##.##.##::32032]] [########-####-####-####-############-HMS-#######] Failed to login to brokered server additional error info: Login request is denied.
Attempt from the source ESXi host failed due to an invalid authentication token, resulting in a denied login request.
Environment
vSphere Live Recovery 9.0.2
Cause
ESXi hosts hbr-agent service is unable to log into vSphere replication appliance due to a network timeout or an invalid broker certificate.
Resolution
HBR broker restarts lead to updates in the BrokerManager.persistenceInstance property, after which HMS pushes the token verification information to all hbrsrvuw instances.
To restart hbrsrv service:
1) SSH into vSphere Replication Appliance and restart hbrsrv service
2) Type 'service restart hbrsrv'
Follow the steps below if restarting HBS services doesn't help.
Reconfigure the vSphere Replication Server with the vCenter Server. This process will push the certificates to the environment and re-establish secure communication between the HBR-Agent and HBR-Srv services.
If there are still issues, restart the hbr-agent and hbrsrv services on source/destination ESXi hosts.
Feedback
