After update to vCenter Server Appliance 6.7 Update 3r, /storage/log fills up sue to growth in content-library-runtime.log.stdout

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• After update to vCenter Server Appliance 6.7 Update 3r, /storage/log fills up sue to growth in content-library-runtime.log.stdout
• When running du /storage/log/vmware | sort -rn | head , one of the highest consumers of disk space is the /storage/log/vmware/content-library directory
  
  When running ls -lSr /storage/log/vmware/content-library | tail , content-library-runtime.log.stdout file is taking up several gigabytes of space
   

 

Environment

VMware vCenter Server 6.7.x

Cause

This issue is due to a regression in the log4j properties file.

Resolution

This issue is resolved in VMware vCenter Server 6.7 Update 3s.

Workaround:
To work around the issue, you can apply the following steps to your vCenter Server Appliance:

1. Connect to the VCSA by means of SSH
2. to resolve the space issue temporarily, purge the content from content-library-runtime.log.stdout:

   # cd /storage/log/vmware/content-library/
   # echo > content-library-runtime.log.stdout  

3. replace the content in /etc/vmware-content-library/log4j.properties with the contents of the file attached to this KB:

   # cd /etc/vmware-content-library/
   # cp -R log4j.properties log4j.properties.old
   # cat /dev/null > log4j.properties
   # vi log4j.properties - insert data from file attached to this document

4. Verify the file ownership/permissions and change accordingly:

   # chown content-library:cis log4j.properties
   # chmod 640 log4j.properties

5. Restart the content library service using:

   # service-control --restart content-library