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

/tmp on ESXi hosts configured for NSX-T may become heavily utilized or full (74574)

Last Updated: 8/31/2019Categories: InformationalTotal Views: 6985Language:
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

On an ESXi host configured for NSX-T Data Center 2.4.x

Scratch is set to default /tmp/scratch

The output of the vdf command shows /tmp is heavily utilized or full

There are multiple log files like this consuming space

/tmp/scratch/log/nsx/metrics/proto_2019_09_01T16-29-56.log

Cause

NSX-T creates proto_<timestamp>.log files in scratch/log/nsx/metrics/. These are binary files which contain metrics collected from the different NSX-T daemons on the ESXi host. These files are intended for use by Engineering when troubleshooting issues on the host.

Resolution

This is a known issue impacting NSX-T 2.4.x and will be resolved in a future version of NSX-T Data Center.

Workaround

It is recommended to configure a scratch partition on ESXi.
If this is not an option e.g. if VSAN is the only storage available then the following workarounds can be used.

Option 1:
Present another storage device to the ESXi hosts e.g. NFS/iSCSI datastore and configure scratch there

or

Option 2:
Enforce a stricter log rotation policy to ensure these files consume less storage space when located in /tmp

1) chmod +t /etc/vmware/nsx-opsagent/nsx-opsAgent.xml
2) Edit /etc/rc.local.d/local.sh.
Add the following 3 lines below the comments section and above the line "exit 0"

chmod +t  /etc/vmware/nsx-opsagent/nsx-opsAgent.xml
sed -i 's/<max_size>1 GiB<\/max_size>/<max_size>40 Mib<\/max_size>/; s/<max_files>50<\/max_files>/<max_files>2<\/max_files>/' /etc/vmware/nsx-opsagent/nsx-opsAgent.xml
/etc/init.d/nsx-opsagent restart

3) Execute the config change by running the updated script
#/etc/rc.local.d/local.sh

Note, this change will persist ESXi host reboot.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
NSX for vSphere 6.4.5 以前のバージョンでの CVE-2019-11477 および CVE-2019-11478 の回避策 (71311)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
NSX-T 备份错误地报告为已成功完成 (71307)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant