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

VM Management Task from vCloud Director takes a long time in a mutiple vCloud Director Cell environment (59206)

Last Updated: 8/21/2023Categories: TroubleshootingTotal Views: 10163Language:
English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

VM Management Tasks such as deploying, powering on and powering off from vCloud Director take a much longer time compared to direct operations via vCenter Server.

Tasks take 20-30 minutes to complete in vCloud

Tasks take longer to complete in vCloud than previously experienced

The following messages can be seen in the /opt/vmware/vcloud-director/logs/cell-runtime.log file :

ERROR| auto-pool-eventPublishing-4-thread-1 | AmqpManagerImpl | Error connecting to AMQP broker with settings '[host=10.x.x.x, port=11006, username=vcloud_user , exchange=vcd, vHost=/, useSSL=false, prefix=vcd]' | java.net.ConnectException: Connection refused (Connection refused)
INFO | ell DiscoveryAgent listener: <LISTENER_UUID>:Thread-93 | CellDiscoveryAgent | REMOVED Failed Cell in Broker Network. Cell UUID: <CELL_UUID>, Broker URI: tcp://x.x.x.x:61616

Cause

This issue is caused by ActiveMQ communication problems between active vCloud Director Cells.

From 8.20, vCloud Director uses an ActiveMQ Message Bus to manage tasks as part of the Distributed Activity Framework.
The Distributed Activity Framework means that a Cell that picks up the Task is no longer required to complete the Task.
As such, the Cells need to be able to update each other on the state of the Task along with who is now running the Task, which is what the ActiveMQ Message Bus is used for.

When there are issues with Cells communicating with the ActiveMQ Message Bus, all Cells in the Server Group will experience issues receiving updates on the status of Tasks.
If the status cannot be obtained via the Message Bus, vCloud Director falls back to performing a Database check and this is where the delays are introduced.

Resolution

Ensure all Cells can communicate to each other over TCP Port 61616

Ensure all Cells are in sync with the same NTP Source

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director for Service Provider

VMware Cloud Director

Related Versions:

VMware Cloud Director for Service Provider 9.x

VMware Cloud Director for Service Provider 9.0.x

VMware Cloud Director for Service Provider 8.20.x

VMware Cloud Director for Service Provider 8.0.x

Take Our Survey

Support Assistant