Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"Assuming task failed, because it's status did not update in a timely fashion" error when configuring replications in Cloud Director Availability 4.x (67776)

Last Updated: 7/27/2023Categories: TroubleshootingTotal Views: 6634Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

When configuring a new outgoing replication, you see the following error in the Replications Tasks view of the Cloud Director Availability Portal:

Assuming task 'b2763219-0fb8-408f-b3a7-1cbf4f110c69' failed, because it's status did not update in a timely fashion.

In /opt/vmware/h4/cloud/log/cloud.log on the Cloud Director Replication Management Appliance on the recovery site, you see a similar message:

2019-04-11 02:13:24.884 DEBUG - [UI_/plugins/Vk13YXJl/h4/outgoing-replications/Provider_Site/vapp_f57cb497-ddda-4147-be26-413ebd52cfdd_K1_4t] [job-3] com.vmware.h4.jobengine.JobEngine        : Suspending execution for task 9a347713-2860-49d7-b18c-1a3358e8273c
2019-04-11 02:13:24.887 DEBUG - [UI_/plugins/Vk13YXJl/h4/outgoing-replications/Provider_Site/vapp_f57cb497-ddda-4147-be26-413ebd52cfdd_K1_4t] [job-3] com.vmware.h4.jobengine.JobEngine        : Suspending execution for task 379f7132-b613-431e-a9a7-ce4e2c32e5d0
2019-04-11 02:13:24.978  WARN - [192edc41-034e-49f1-9aaa-3016081d018b] [c4-scheduler-2] com.vmware.task.rest.client.TaskMonitor  : Task b2763219-0fb8-408f-b3a7-1cbf4f110c69 has timed out (it hasn't been updated in 60000 msec)
2019-04-11 02:13:24.983 ERROR - [UI_/plugins/Vk13YXJl/h4/outgoing-replications/Provider_Site/vapp_f57cb497-ddda-4147-be26-413ebd52cfdd_K1_4t] [c4-scheduler-2] com.vmware.h4.jobengine.JobExecution     : Task 9a347713-2860-49d7-b18c-1a3358e8273c (WorkflowInfo{type='start', resourceType='vmReplication', resourceId='C4-0c68766f-9ad5-4dee-a188-c45f1d8aac03', isPrivate=false, resourceName='null'}) has failed
com.vmware.vdr.error.exceptions.TaskMonitoringTimeOutException: Assuming task 'b2763219-0fb8-408f-b3a7-1cbf4f110c69' failed, because it's status did not update in a timely fashion.
at sun.reflect.GeneratedConstructorAccessor146.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.vmware.h4.exceptions.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:70)
at com.vmware.h4.exceptions.GenericServerExceptionProvider.get(GenericServerExceptionProvider.java:47)
at com.vmware.h4.common.task.H4ApiTaskToTaskConverter.toTask(H4ApiTaskToTaskConverter.java:33)
at com.vmware.task.rest.client.TaskMonitor.lambda$workImpl$0(TaskMonitor.java:189)
at com.vmware.task.rest.client.TaskMonitor.notifyListener(TaskMonitor.java:211)
at com.vmware.task.rest.client.TaskMonitor.workImpl(TaskMonitor.java:188)
at com.vmware.task.rest.client.TaskMonitor.work(TaskMonitor.java:120)
at com.vmware.task.rest.client.TaskMonitorService.lambda$taskMonitor$0(TaskMonitorService.java:65)
at com.vmware.h4.common.mdc.MDCRunnableWrapper.run(MDCRunnableWrapper.java:30)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue can occur when there is a time drift between the Cloud Director Availability components on the protected and recovery sites.

Resolution

To resolve this issue, configure the following time settings across all sites:

In each cloud site, ensure the Tunnel Appliance, Cloud Director Replication Management Appliance, Replicator Appliance(s), Cloud Director cells, vCenter Server(s), Platform Services Controller, and ESXi Hosts have their times synced to the same NTP source.

In each on-premises site, ensure the Cloud Director Availability On-Premises Appliance, vCenter Server, Platform Services Controller, and ESXi Hosts have their times synced to the same NTP source.

Ensure that all sites have their times in sync with each other by either synchronising to the same NTP source or having each site's own NTP server further synchronise to the same upstream NTP source.

Related Information

This error can also be generated when there are multiple offline or inaccessible Replicator appliances or there is a delay interacting with and processing API calls to the destination vSphere environment.

For more information, see:

Migration and replication tasks fail because the task status did not update in a timely fashion in Cloud Director Availability 4.x

Configuring new replications time out while waiting for the setup destination task to complete in Cloud Director Availability 4.x

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
将 vSAN VMDKS 从一个命名空间文件夹移动到另一个命名空间文件夹不会更新对象路径属性 (70774)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware Cloud Director Availability 4.x

Take Our Survey

Support Assistant