vmsupport files left on ESX or ESXi host fill the filesystem on which they reside

Products

• VMware

Issue/Introduction

Symptoms:

• ESX (or ESXi) host system logs have been exported from the vSphere (or Virtual Infrastructure) Client several times since the host was built.
• On an ESX host, the (/) root directory or /usr directory filesystem is full. On an ESXi host, the scratch filesystem is full.

Resolution

When the host logs are exported using the vSphere/Virtual Infrastructure Client, there is a vmsupport.tgz file left behind on the host. On an ESX host, this file resides in /usr/lib/vmware/hostd/docroot/downloads. On an ESXi host, this file resides in /scratch/downloads. There is no automatic mechanism to clean up these files. Given enough time and log exports, these files could fill the file systems on which they reside.

This issue is resolved in ESX\ESXi 4.1, Update 1. For more information, see VMware ESX 4.1 Update 1 Release Notes available at VMware Downloads.

To work around this issue, prevent these file systems from filling up.

To prevent these file systems from filling up, perform one of these two procedures:

1. Periodically check for the existence of these files and delete them as appropriate.
2. Implement a cron job to call a custom script that cleans these files.
   1. Use a text editor to create a script in /usr/local/bin on ESX or in /scratch on ESXi.
      
   2. Add these lines to the newly created script:

daterange="30"
esxidir="/scratch/downloads"
esxdir="/usr/lib/vmware/hostd/docroot/downloads"
if [ -d $esxidir ]
then
find $esxidir -name \*support-*.tgz -mtime +$daterange -exec rm -f {} \;
else
find $esxdir -name \*support-*.tgz -mtime +$daterange -exec rm -f {} \;
fi

Replace the "30" for the daterange variable with the number of days the vmsupport files should be left on the system.

1. Make the script executable, chmod +x /usr/local/bin/

Additional Information

Using Tech Support Mode in ESXi 4.1, ESXi 5.x, and ESXi 6.x