/tmp ramdisk directory of an esxi host can be full with "vim-cmd*.txt" files due to nsx-exporter OOM.

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

/tmp ramdisk is full with "vim-cmd*.txt" files and it is detected in /var/run/log/vmkwarning.log.

<DATE_TIME> Wa(180) vmkwarning: cpu15:177078748)WARNING: VisorFSObj: 1958: Cannot create file /tmp/vim-cmd-#########-##########.txt for process vim-cmd because the inode table of its ramdisk (tmp) is full.

"Admission failure" is seen in /var/run/log/vmkernel.log.

<DATE_TIME> In(182) vmkernel: cpu23:177078888)Admission failure in path: host/vim/vmvisor/nsx-exporter:vim-cmd.<UserWorld_ID>:uw.<UserWorld_ID>

And "Failed to get bfd info" is seen in /var/run/log/nsx-syslog.log.

<DATE_TIME> Er(179) nsx-exporter[2101062]: NSX 2101062 - [nsx@6876 comp="nsx-esx" subcomp="agg-service" tid="2101443" level="ERROR" errorCode="MPA12104"] [Heatmap][GetTunnelsStatus] Failed to get bfd info for dvs <DVS_NAME>

 

Environment

VMware NSX-T

VMware NSX

Cause

If an esxi host has more than 1 DVS, e.g., the one is overlay DVS, the other is non-overlay(VLAN segment) DVS, it will cause memory leak of the nsx-exporter process.

Resolution

This issue is addressed in NSX 3.2.4, 4.2.0.

Workaround:

To address this issue, restart the nsx-exporter service and remove vim-cmd*.txt files in /tmp directory but it is the temporary workaround.

• Stop the nsx-exporter service: /etc/init.d/nsx-exporter stop 
• Start the nsx-exporter service: /etc/init.d/nsx-exporter start