2025-05-14T12:51:52.670Z info hbrsrv[00956] [Originator@6876 sub=Delta] Destroying client connection (ClientCnx '[#.#.#.#]:51648' id=0 <shut> <clsd> <uninit>)
2025-05-14T12:51:55.817Z warning hbrsrv[00948] [Originator@6876 sub=Stats] ScheduleUpdate cannot find obj for Hbr.Replica.Group.H4-#####-#####-####-####-####
2025-05-14T12:51:55.817Z warning hbrsrv[00948] [Originator@6876 sub=Stats] ScheduleUpdate cannot find obj for Hbr.Replica.Group.H4-#####-#####-####-####-####
2025-05-14T12:51:55.817Z warning hbrsrv[00948] [Originator@6876 sub=Stats] ScheduleUpdate cannot find obj for Hbr.Replica.Group.H4-#####-#####-####-####-####
2025-05-14T12:51:55.817Z warning hbrsrv[00948] [Originator@6876 sub=Stats] ScheduleUpdate cannot find obj for Hbr.Replica.Group.H4-#####-#####-####-####-####
2025-05-14T12:51:55.817Z info hbrsrv[00948] [Originator@6876 sub=Delta] ClientConnection (ClientCnx '[#.#.#.#]:33434' id=5 <shut>) is stopping ...
2025-05-14T12:51:55.817Z info hbrsrv[00948] [Originator@6876 sub=Asio] Closing LWD ASIO -> (plain text)
2025-05-14T12:51:55.817Z info hbrsrv[00948] [Originator@6876 sub=Delta] HbrSrv cleaning out ClientConnection ([#.#.#.#]:33434)
2025-05-14T12:51:55.817Z error hbrsrv[00948] [Originator@6876 sub=Main] HbrError stack:
2025-05-14T12:51:55.817Z error hbrsrv[00948] [Originator@6876 sub=Main] [0] ClientConnection (client=[#.#.#.#]:33434) request callback failed: Failed to read: End of file
2025-05-14T12:51:55.817Z error hbrsrv[00948] [Originator@6876 sub=Main] [1] Dropping error encountered from network
2025-05-14T12:51:55.818Z info hbrsrv[00948] [Originator@6876 sub=StatsLog] HbrEvent: {"eventID":"lwdConnectionReset","groupID":"H4-#####-#####-####-####-####","clientAddress":"[#.#.#.#]:33434","serverID":"#####-#####-####-####-####","hbrEvent":1}
VMware Cloud Director Availability
This issue occurs when the replicator is placed in maintenance mode when there are active tasks associated with it.
VMware Cloud Director Availability replicator should not be placed in maintenance mode when there are active tasks associated with them.
For more information about placing replicator in maintenance mode, please refer Replicator Service maintenance mode .