Error: "Timeout has occurred" when attempting to create cold migrations
search cancel

Error: "Timeout has occurred" when attempting to create cold migrations

book

Article ID: 430880

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

  • When attempting to create cold migrations from the Cloud Director Availability UI it fails with the following error:

    "Timeout has occurred"

  • In the /opt/vmware/h4/cloud/log/cloud.log on the source Cloud Director Availability management appliance you will see log entries similar to below:

    2026-02-24 15:27:52.592  WARN - [########-####-####-####-############] [health-check-9] c.vmware.h4.cloud.service.H4dmConnector  : An exception occurred while attempting to reconnect to the Data Mover.

    com.vmware.exception.ConnectTimeout: Connect to ###.###.###.###:3030 [/###.###.###.###] failed: Connect timed out
            at com.vmware.exception.converter.ClientExceptionConverter.convertException(ClientExceptionConverter.java:40)
            at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:162)
            at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:106)
            at com.vmware.rest.client.AbstractRestClient.genericExchange(AbstractRestClient.java:91)
            at com.vmware.rest.client.base.BaseRestClient.exchange(BaseRestClient.java:46)
            at com.vmware.h4dm.client.H4dmClient.diagnostics_about(H4dmClient.java:912)
            at com.vmware.h4.cloud.client.H4dmHealthMonitor.onCreated(H4dmHealthMonitor.java:23)
            at com.vmware.h4.cloud.client.H4dmHealthMonitor.onCreated(H4dmHealthMonitor.java:16)
            at com.vmware.resource.health.HealthCheckingFactory$1.acquire(HealthCheckingFactory.java:107)
            at com.vmware.resource.CachedResourceFactory.acquire(CachedResourceFactory.java:135)
            at com.vmware.resource.CachedResourceFactory.acquire(CachedResourceFactory.java:84)
            at com.vmware.h4.cloud.service.H4dmConnector.acquire(H4dmConnector.java:67)
            at com.vmware.h4.cloud.service.H4dmConnector.reconnectOffline(H4dmConnector.java:57)
            at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:32)
            at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
            at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
            at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
            at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
            at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
            at java.base/java.lang.Thread.run(Thread.java:840)
    Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to ###.###.###.###:3030 [/###.###.###.###] failed: Connect timed out

Environment

VMware Cloud Director Availability 4.x 

Cause

This issue occurs when the Cloud Director Availability management appliance attempts to use a replicator for cold migrations that has already been decommissioned and removed from the environment.

Resolution

To resolve this issue, disable / enable cold migrations within the Cloud Director Availability UI. enabling and disabling this setting forces the Cloud Director Availability manager to select a new, active replicator for future cold migrations.

Please review Activate cold migrations for more information.

Note: enabling / disabling cold migrations will delete any pre-existing cold migration templates

Powered by Wolken Software