Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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 /var/log partition grows exponentially without rotating on VMware NSX-T Controller Node (74758)

Last Updated: 9/17/2019Categories: TroubleshootingTotal Views: 4962Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

In the NSX-T 2.3.x dashboard, you see disk usage alert for controller node similar to:
Disk usage is high for filesystem /dev/mapper/nsx-var+log

When you check the volume mount information on the controller, you see that /var/log/moot-server/Zookeeper_0  directory taking up most of the space.

You see that zookeeper.log, zookeeper-cli.log files does not get compressed.

Cause

The issue occurs as the log rotation does not work as expected.

Impact / Risks

This will cause the control plane to malfunction as the moot service (which is a container for zookeeper) will stop. Due to this zookeeper may not start and control cluster will be impacted. So controller will not function as expected.

Resolution

This is a known issue with VMware NSX-T 2.3.0 and 2.3.1.

This issue is resolved in VMware NSX-T 2.4.1 and later.

Workaround

To work around this issue in NSX-T 2.3.x, change the log file rotation parameters as mentioned below on the problematic Controller node:

Log in to Controller node as root user.

Edit the log4j.properties file located at:
/config/moot-server/localServiceManager/containers/Zookeeper/persistentStore/zkWorkspace

Update the following parameters:
zookeeper.log.maxfilesize=256MB
zookeeper.log.maxbackupindex=20
Set these values as per the requirement and free space on controller node.

Validate the changes:
# /var/log/moot-server/Zookeeper_0# grep "zookeeper.log.maxfilesize\|zookeeper.log.maxbackupindex" /config/moot-server/localServiceManager/containers/Zookeeper/persistentStore/zkWorkspace/log4j.properties
zookeeper.log.maxfilesize=128MB
zookeeper.log.maxbackupindex=5

Restart the controller to apply the changes.

Note: Changes on the log4j.properties will be persistent after the reboot of the controller only. Changes will not be reflecting if you do service restart like this /etc/init.d/moot-server restart

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

nsx_controller_disk_usage

Additional Resources

KB
•
应用热修补程序后，Usage Meter 无法导出日志包并发送未加密的报告 (74693)

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 PKS

Related Versions:

VMware PKS 1.x

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant