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

The vCenter proxy service fails to start on Cloud Director cells while Cloud Proxy cells are active (53172)

Last Updated: 8/17/2023Categories: TroubleshootingTotal Views: 8261Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

In System > Manage & Monitor > Cloud Cells of the vCloud Director UI, you may see the following message:

None of the cells have a vCenter proxy service running.

In System > Manage & Monitor > vCenters of the vCloud Director UI one or more of the resource vCenters show as disconnected.

Attempting to reconnect to a disconnected vCenter may fail with the following error:

Unable to communicate with the cell to start the listener.

In /opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the vCloud Director cells, you may see the following messages:

2018-03-12 15:26:38,099 | DEBUG    | CoordinatorJob            | VimProxyFailoverService        | Found 1 VC proxies that need to be started on 5 available candidate cells. |
2018-03-12 15:26:38,099 | DEBUG    | CoordinatorJob            | VimProxyFailoverService        | Generated 1 recommendations for VC execution |
2018-03-12 15:26:38,099 | DEBUG    | CoordinatorJob            | VimProxyFailoverService        | Will execute 1 recommendations in this coordinator run. |
2018-03-12 15:26:38,099 | INFO     | CoordinatorJob            | VimProxyFailoverService        | Starting VC Proxy for VC <VC_UUID> on cell <CELL_NAME>|
2018-03-12 15:26:38,100 | DEBUG    | CoordinatorJob            | FailoverMessageServiceImpl     | Published JMS message ID:vcd.example.com-40916-1520593351795-4:2:4:1:16287 |
2018-03-12 15:26:38,100 | DEBUG    | ActiveMQ Session Task-830 | FailoverMessageServiceImpl     | Received JMS message ID:vcd.example.com-40916-1520593351795-4:2:4:1:16287 |
2018-03-12 15:26:38,100 | DEBUG    | CoordinatorJob            | FailoverMessageServiceImpl     | Published request [id = failoverMessage-cid:<CID>-ciid:3141-mid:16287, type = Request, src instance = 141 (id = <INSTANCE_UUID>), target instance = <CELL_NAME>, timestamp = Mon Mar 12 15:26:38 CET 2018] (JMS message ID {1}). |
2018-03-12 15:26:38,100 | DEBUG    | ActiveMQ Session Task-830 | FailoverMessageServiceImpl     | Received message [id = failoverMessage-cid:<CID>-ciid:3141-mid:16287, type = Request, src instance = 141 (id = <INSTANCE_UUID>), target instance = <CELL_NAME>, timestamp = Mon Mar 12 15:26:38 CET 2018] on cell instance 141 |

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

Cause

This issue occurs because the Cloud Proxy cells are being considered as viable cells that the vCenter Proxy can be run on.

This can occur when existing vCloud Director cells are cloned and reconfigured to act as a Cloud Proxy.

This can occur if the vCloud Director services were started on a Cloud Proxy before its /opt/vmware/vcloud-director/etc/global.properties file was modified to make the cell a dedicated Cloud Proxy.

Resolution

To resolve this issue, problematic Cloud Proxies should be removed from the vCloud Director instance and new Cloud Proxies should be created on new VMs and not cloned from existing vCloud Director cells.

Note: The vCloud Director services should only be started after the cell has been configured as a dedicated Cloud Proxy.

To remove an existing Cloud Proxy from a vCloud Director instance, perform the steps below.

SSH as root to the Cloud Proxy cell.

Stop the vCloud Director services on the Cloud Proxy cell:

service vmware-vcd stop

In the vCloud Director UI navigate to System > Manage & Monitor > Cloud Cells.

Right-click on the stopped Cloud Proxy cell name and click Delete.

Workaround

To work around this issue, perform the following steps:

SSH to each of the Cloud Proxies.

Stop the vCloud Director services on the Cloud Proxies with the following command:

service vmware-vcd stop

In the vCloud Director GUI navigate to System > Manage & Monitor > vCenters.

Right-click on the vCenter Server that is showing as disconnected and click Reconnect.

After the vCenter has been reconnected start the vCloud Director services on the Cloud Proxies with the following command:

service vmware-vcd start

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
在 vRealize Operations Manager 6.x 及高级版本中，“数据存储群集摘要”显示“已打开电源的虚拟机”数量为问号 (53124)

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 8.x

Take Our Survey

Support Assistant