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

Log files are no longer logging messages in vCloud Director Appliance (74718)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 2836Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Log files are no longer logging messages in vCloud Director Appliance.

Cause

This issue occurs because the vCloud Director Appliance has ran out of disk space.

Resolution

To resolve this issue, Increase the size of the root (/) filesystem.

Notes:

These instructions use the "parted" utility as part of the process for increasing the root filesystem size. This only works when the partition where the root filesystem resides is the last partition on the disk.

Execute these instructions starting with standby appliance(s) and finish with the primary appliance.

Using the vSphere User Interface, increase the physical size of the disk used by the root filesystem:
In the following example the original size of hard disk 1 was 30GB. We are increasing it to 60GB.

a. Select the VM of the appliance you want to increase the storage.
b. Select Actions > Edit settings.
c. Hard disk 1 is where the root filesystem resides. Increase the size to the desired amount.
d. click OK.

If parted is not installed on the appliance, install it using the tdnf command. Open an SSH session on the appliance logging in as root user.

Before continuing, the operating system needs to recognize the change in physical disk size. Execute the following command in the ssh session:
echo 1 > /sys/class/block/sda/device/rescan

Extend the disk partition that is used by the root filesystem using the parted command. The root hard disk is /dev/sda.

a. Use the print command from within parted to display partition information about the hard disk.
b. A warning will be displayed that not all of the available space is being used. Type Fix to claim the newly requested space.
c. After the print command completes, note that the hard disk /dev/sda is now increased (in this case 64.4GB).
d. Use the resizepart command from within parted to expand the partition that is being used by the root filesystem.

Expand the filesystem to the increased size of the partition using resize2fs and verify that the filesystem has increased using df.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
在 VMware NSX-T Controller 节点上，/var/log 分区呈指数增长，而不进行轮换 (74758)

KB
•
ホット パッチを適用した後、使用量メーターがログ バンドルのエクスポートに失敗し、暗号化されていないレポートを送信する (74693)

Results 1-2 of 2

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