vCenter /storage/log filling up due to /storage/log/storage/log/vmware/vc-ws1a-broker directory.

Products

• VMware vCenter Server 8.0

Issue/Introduction

You observe the "log disk exhaustion" warning on the vCenter Server.
When running du /storage/log/vmware | sort -rn | head , one of the highest consumers of disk space is the /storage/log/storage/log/vmware/vc-ws1a-broker directory.

du /storage/log/vmware | sort -rn | head
7.0G    /storage/log/vmware
7.0G    /storage/log/
2.4G    /storage/log/vmware/vc-ws1a-broker
712M    /storage/log/vmware/wcp
609M    /storage/log/vmware/vsphere-ui
505M    /storage/log/vmware/vsphere-ui/logs

 
You see a large number of *-gc.log in /storage/log/vmware/vc-ws1a-broker directory. 

/storage/log/vmware/vc-ws1a-broker
51M accesscontrol-gc.log.0
51M accesscontrol-gc.log.1
51M accesscontrol-gc.log.2
51M accesscontrol-gc.log.3
51M crypto-gc.log.0
51M crypto-gc.log.1
51M crypto-gc.log.2
51M crypto-gc.log.3
51M crypto-gc.log.4
51M federation-gc.log.0
51M federation-gc.log.1
51M federation-gc.log.2
51M federation-gc.log.3
51M token-gc.log.0
51M token-gc.log.1
51M token-gc.log.2
51M token-gc.log.3
51M token-gc.log.4
51M usergroup-gc.log.0
51M usergroup-gc.log.1
51M usergroup-gc.log.2
51M usergroup-gc.log.3
51M usergroup-gc.log.4

 

Environment

VMware vCenter Server 8.0 U1
VMware vCenter Server 8.0 U2

Cause

Garbage collector logs for vc-ws1a-broker isn't compressed appropriately.

Resolution

This issue is resolved in vCenter Server 8.0 U3.

Workaround:
Removing old garbage collector logs.
for examples:
find /storage/log/vmware/vc-ws1a-broker -name "*-gc.log.*" -exec rm {} \;