Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When vSphere Replication appliance reboots, the VR appliance shows disconnected and you see a message similar to: A generic error occurred in the vSphere Replication Management Server. java.net.ConnectException: 'java.net.ConnectException: Connection refused' In the hms.log, you see the message similar to: 2018-02-27 02:07:20.481 DEBUG hms.replication.secondaryGroup [hms-main-thread-29] (..hms.replication.SecondaryGroupImpl) operationID=802c46e9-ac7e-4812-9350-1f22b72b5a00-HMS-35336 operationID=802c46e9-ac7e-4812-9350-1f22b72b5a00-HMS-35336 | Creating replication group hostname (GID-46526c97-9675-416f-b218-c7d2014308a5) at HBRsrv 192.168.1.XX...FAILEDcom.vmware.vim.vmomi.client.exception.ConnectionException: java.net.SocketTimeoutException: Read timed out at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:251) at com.vmware.vim.vmomi.client.http.impl.HttpExchange.run(HttpExchange.java:54) at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:186) at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:115) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.sendCall(MethodInvocationHandlerImpl.java:581) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl$CallExecutor.executeCall(MethodInvocationHandlerImpl.java:562) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.completeCall(MethodInvocationHandlerImpl.java:348) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invokeOperation(MethodInvocationHandlerImpl.java:308) at com.vmware.vim.vmomi.client.common.impl.MethodInvocationHandlerImpl.invoke(MethodInvocationHandlerImpl.java:182) at com.sun.proxy.$Proxy170.createGroup(Unknown Source) at com.vmware.hms.replication.SecondaryGroupImpl.configureHbrServer(SecondaryGroupImpl.java:1703) at com.vmware.hms.hbr.HbrService.createHbrGroup(HbrService.java:53) at com.vmware.hms.job.impl.ConfigureReplicationSecondaryImpl.createHbrGroup(ConfigureReplicationSecondaryImpl.java:126) at com.vmware.hms.job.impl.ConfigureReplicationSecondaryImpl.go(ConfigureReplicationSecondaryImpl.java:88) at com.vmware.hms.task.TaskRunnable.run(TaskRunnable.java:31) at com.vmware.hms.util.executor.LoggerOpIdConfigurator$RunnableWithDiagnosticContext.run(LoggerOpIdConfigurator.java:133) at com.vmware.hms.util.executor.LoggerOpIdConfigurator$2.run(LoggerOpIdConfigurator.java:100) at com.vmware.jvsl.sessions.net.impl.TlsPreservingWrapper$2.run(TlsPreservingWrapper.java:47) at com.vmware.jvsl.executors.ThrottledExecutorService$1.run(ThrottledExecutorService.java:136) at com.vmware.hms.util.executor.LoggerOpIdConfigurator$RunnableWithDiagnosticContext.run(LoggerOpIdConfigurator.java:133) at com.vmware.hms.util.executor.LoggerOpIdConfigurator$2.run(LoggerOpIdConfigurator.java:100) at com.vmware.jvsl.sessions.net.impl.TlsPreservingWrapper$2.run(TlsPreservingWrapper.java:47) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Unable to start VRM service.
This article provides information to recover form VMware vSphere Replication appliance disconnected status as a VR Server.
This issue occurs if SRM planed Reprotect recovery plan is executed.
This is a known issue affecting VRA 6.0.x, 6.1.0 and 6.1.1.Currently, there is no resolution.
To workaround this issue: Stop hbrsrv service service hbrsrv stop Take a backup of hbrsrv service Database: cp /etc/vmware/hbrsrv.54.db /etc/vmware/hbrsrv.54.db.bak Check the hosts which are registered in DB sqlite3 /etc/vmware/hbrsrv.54.db "select * from HostInfo"; Delete the hosts which hbr cannot connect after backup: DELETE FROM HostInfo WHERE addresses in ('IP address 1','IP address 2', 'IP address 3'); Check the hosts which are removed from DB sqlite3 /etc/vmware/hbrsrv.54.db "select * from HostInfo;" Restart hbrsrv service: service hbrsrv start Wait for 30 min after after host gets connected. Note: If Hosts are not visible in inventory in vCenter Server, hbrsrv service DB will register unreachable hosts after VR appliance reboot.