The Wrath of the Syslog Debug File

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!

Screenshot 2015-08-27 11.27.33

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.

  1. log on to the vCenter server
  2. Stop the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895)Screenshot 2015-08-27 11.27.51
  3. On the server running the VMware Syslog Collector service, navigate to C:ProgramDataVMwareVMware Syslog Collector and save a copy of vmconfig-syslog.xml.
  4. In a text editor, open vmconfig-syslog.xml and modify  from:

    <debug> <level>1</level> </debug>

    to

    <debug> <level>0</level> </debug>

  5. Start the VMware Syslog Collector service. For more information, see Stopping, starting, or restarting VMware vCenter Server services (1003895).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s