SRM/vSphere replication site pair failing with Unable to retrieve pairs from extension server at https://#########.com:8043.A generic error occurred in the vSphere Replication Management Server. Exception details: 'Error creating bean with name 'com.vmware.hms.remote.HmsServerImpl': Unsatisfied dependency expressed through field 'repositoryFactory'; nested exception is org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'repositoryFactory': Singleton bean creation not allowed while singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)'.
hbrsrv.log
2025-05-13T22:00:32.166Z error hbrsrv[01247] [Originator@6876 sub=Main] HbrError stack:
2025-05-13T22:00:32.166Z error hbrsrv[01247] [Originator@6876 sub=Main] [0] ClientConnection (client=[2620:10d:####:103::##]:60690) request callback failed: Connection reset by peer: The connection is terminated by the remote end with a reset packet. Usually, this is a sign of a network problem, timeout, or service overload.
2025-05-13T22:00:32.166Z error hbrsrv[01247] [Originator@6876 sub=Main] [1] Dropping error encountered from network
2025-05-13T22:00:32.166Z info hbrsrv[01247] [Originator@6876 sub=StatsLog] HbrEvent: {"eventID":"lwdConnectionReset","groupID":"GID-####-2560-####-b9c2-####","clientAddress":"[####:10d:c085:103::83]:60690","serverID":"52a8a8b3-####-a013-####-fc80e65a1111","hbrEvent":1}
2025-05-13T22:00:32.166Z info hbrsrv[01247] [Originator@6876 sub=Delta] Destroying client connection (ClientCnx '[2620:10d:####:103::83]:60690' id=168848 <shut> <clsd>)
2025-05-13T22:00:32.166Z info hbrsrv[01247] [Originator@6876 sub=Misc] Client session 1 disconnected from group GID-####-2560-####-b9c2-####.
2025-05-13T22:00:32.167Z info hbrsrv[01257] [Originator@6876 sub=Delta] Changing group GID-####-2560-####-b9c2-#### state from opened to passive
2025-05-13T22:00:32.167Z verbose hbrsrv[01257] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: state, Hbr.Replica.Group.GID-####-2560-####-b9c2-####. Applied change to temp map.
2025-05-13T22:00:33.420Z verbose hbrsrv[01964] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: hostStatsSet, Hbr.Replica.Host.host-2095. Applied change to temp map.
2025-05-13T22:00:34.168Z verbose hbrsrv[01986] [Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: hostStatsSet, Hbr.Replica.Host.host-2089. Applied change to temp map.
2025-05-13T22:00:34.268Z info hbrsrv[01247] [Originator@6876 sub=Main] HbrError stack:
2025-05-13T22:00:34.268Z info hbrsrv[01247] [Originator@6876 sub=Main] [0] Database object not found
2025-05-13T22:00:34.268Z info hbrsrv[01247] [Originator@6876 sub=Main] [1] Looking up global key in the database guestinfo.hbr.hbrsrv-certificate-revoked/guestinfo-cache
2025-05-13T22:00:34.268Z info hbrsrv[01247] [Originator@6876 sub=Main] [2] Couldn't read cached value for key guestinfo.hbr.hbrsrv-certificate-revoked
2025-05-13T22:00:34.268Z info hbrsrv[01247] [Originator@6876 sub=Main] [3] Ignored error.
VMware vCenter 8.0.3
VMware Live recovery 9.0.2
VMware vSphere replication 9.0.2
This issue is caused by vSphere replication server loosing network connectivity because of DHCP. When Site recovery manager or vSphere replication is deployed with IPV6 it automatically Enable DHCP even when we select Static IP during deployment. As a result it shows Multiple IPV6 addresses for ETH0. When we try to remove the incorrect IPV6 addresses from VAMI it will not work. Even Assigning the correct IPV6 address from command line will not work.
1.SSH into vSphere replication appliance
2. Navigate to /etc/systemd/network
3. Edit eth0 and change the linklocaladdress=no
4. Reboot the vSphere replication appliance