vCenter /storage/log directory filling up due to /storage/log/vmware/vc-ws1a-broker log files
search cancel

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

book

Article ID: 397148

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

  • There is a "log disk exhaustion" warning on the vCenter Server.
  • When running the command:
    du /storage/log/vmware | sort -rn | head
    one of the highest consumers of disk space is the /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

 There are a large number of *-gc.log files in the /storage/log/vmware/vc-ws1a-broker directory:

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

Environment

VMware vCenter Server 8.0 U1
VMware vCenter Server 8.0 U2

Cause

The garbage collector logs for vc-ws1a-broker are not compressed correctly.

Resolution

The issue is resolved in vCenter Server 8.0 U3.

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