So I came across this one today the vCenter server had previously been upgraded from 5.1 to 5.5 and the Syslog Collector had also been installed on that server. We noticed that the C Drive had started to fill up over a period of time and traced that back to the following file.
C:ProgramDataVMwareVMware Syslog Collectorlogsdebug.log which was now 15GB in size!
It turns out thanks to KB 2094175 that this is a known issue with no known resolution apart from to carry out the following tasks.
- log on to the vCenter server
- Stop the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895)
- On the server running the VMware Syslog Collector service, navigate to C:ProgramDataVMwareVMware Syslog Collector and save a copy of vmconfig-syslog.xml.
- In a text editor, open vmconfig-syslog.xml and modify from:
<debug> <level>1</level> </debug> to<debug> <level>0</level> </debug>
- Start the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895).
