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

Cell "FAIL" status for Multi-Cell Log Collection (71349)

Last Updated: 8/18/2023Categories: TroubleshootingTotal Views: 13386Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When running vmware-vcd-support script with the following options (-l -m) to gather logs from all cells in the server group, the tool's "Tool Executed Status" may return a "FAIL" status for one or more of the cells.  For example:

Tool Executed Status
LogCollector(MultiCell)

CELLID#

<CELL_UUID> FAIL

Cause

When running vmware-vcd-support script with the "-l -m" options to gather logs from all cells in the server group, the tool may attempt to gather logs from cells which have been decommissioned and removed from the server-group inventory.

Consider the case where, the customer has a vcd server-group with 3 cells. And recently two of those cells have been decommissioned and replaced by two new cells. During the decommissioning of the two cells, the old cells have been removed from the vcd inventory using the delete option in Flex UI > System > Manage & Monitor > Cloud Resources > Cloud Cells.

In the above case, the following sample output would be shown when running "/opt/vmware/vcloud-director/bin/vmware-vcd-support -l -m".

YYYY-MM-DD HH:MM:SS | INFO | Support directory created successfully
YYYY-MM-DD HH:MM:SS | INFO | Output directory created successfully.
YYYY-MM-DD HH:MM:SS | INFO | Collecting multi cell logs...
Collecting logs... [Time to timeout: 30 seconds]
Log bundle created: /opt/vmware/vcloud-director/data/transfer/vmware-vcd-support/bundles/logs_YYYY-MM-DD_HHMMSSUTC.tgz
Logs from following cells may not have been included in the bundle: <CELL4_UUID> <CELL5_UUID>

***VMware vCD Support Execution Summary***

Tool Executed Status

LogCollector(MultiCell)

CELLID#

<CELL1_UUID> PASS
<CELL2_UUID> PASS
<CELL3_UUID> PASS
<CELL4_UUID> FAIL
<CELL5_UUID> FAIL
----------------------------------------------------------------------------
YYYY-MM-DD HH:MM:SS | INFO | Support information has been collected and saved as /opt/vmware/vcloud-director/data/transfer/vmware-vcd-support/vmware-vcd-support-2019-07-11.27223.tgz.

FAIL is reported for the support bundle generation on two vcd cells, those with the following <CELL4_UUID>, <CELL5_UUID>.

Those UUIDs are related to the cells that have been decommissioned. To confirm, one would need to either check the cells table in the vcloud database, or can check the "vcloud.cell.uuid" field in the /opt/vmware/vcloud-director/etc/global.properties file on each remaining cell in the server-group. These two UUIDs should not be found in either source location.

The vmware-vcd-support tool use a different cells ID list, other than the current entries in the cells table, to determine which cells it should generate support bundles. The list comes from the cells directory in the transfer share. /opt/vmware/vcloud-director/data/transfer/cells/ directory. Each file in that directory maps to an existing or decommissioned vcd cell in that server-group.

Here is a sample output from that directory.

ls -ltr
total 0
rwxr-x-- 1 1003 1002 0 Jan 1 1970 <CELL1_UUID>
rwxr-x-- 1 1003 1002 0 Jan 2 1970 <CELL2_UUID>
rwxr-x-- 1 1003 1002 0 Jan 2 1970 <CELL3_UUID>
rw------ 1 1003 1002 0 Jan 2 1970 <CELL4_UUID>
rwxr-x-- 1 1003 1002 0 Jan 2 1970 <CELL5_UUID>

In this case, since the support bundle tool did successfully collect support bundles for 3 cells, and only 3 cells are active, the two failure messages can be assumed to be a benign error can be safely ignored.

Resolution

To workaround the issue, identify the UUID's for all the currently active VCD cells that are part of the server-group, and delete the files in /opt/vmware/vcloud-director/data/transfers/cells that are NOT part of that active set/list.

Note: When VCD cell service is restarted, it recreates its unique file in /opt/vmware/vcloud-director/data/transfers/cells if it does not already exist.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
对文件 /opt/vmware/vcloud-director/data/transfer 解压存档失败：cpio：chown (71340)

KB
•
使用 Cohesity 保护 vCloud Director 环境 (71326)

KB
•
尝试通过 api 删除计算机前缀时出现错误“400 错误请求 (400 bad request)” (71344)

KB
•
新しいプロバイダ VDC を作成するときに、ストレージ ポリシーが表示されない (71321)

KB
•
Usage Meter 无法完成 vROPS 配置 (71305)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

Take Our Survey

Support Assistant