Configuring the wrapper.log file to prevent it from getting too large in VMware vCenter Server 5.0.x/5.1.x

Products

• VMware vCenter Server

Issue/Introduction

This article provides information on configuring settings on the Wrapper.log file to prevent it from growing to an uncapped size.

Symptoms:

• The size of the wrapper.log file (located at C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs) in vCenter Server 5.0.x/5.1.x grows to a large size.
• The wrapper.log file grows to 25 GB or more.

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 5.0.x

Resolution

To resolve this issue, configure the settings for the wrapper.log file.

To configure the settings for the wrapper.log file:

1. Stop the VMware VirtualCenter Server service that also stops the vCenter Inventory service. For more information, see Stopping, starting or restarting vCenter services (1003895).
2. Take a backup of the wrapper.log. For example:
   
   Copy the wrapper.log file to a different drive or location with enough space. Then delete the existing original wrapper.log file from C:\ProgramData\VMware\Infrastructure\Inventory Service\Logs.
   
   
   
3. Open the wrapper.conf file (located at C:\Program Files\VMware\Infrastructure\Inventory Service\conf) using a text editor.
4. Change the value of the wrapper.logfile.maxsize parameter from 0 to 100m .
5. Change the value of the wrapper.logfile.maxfiles parameter from 0 to 2. For example:
   
   wrapper.logfile.maxsize=100m
   wrapper.logfile.maxfiles=2
   
   Note: This ensures that the maximum file size of the wrapper.log file is 100 MB and the maximum number of rolled log files that are allowed before old files are deleted is 2.
   
   
6. Restart the VMware VirtualCenter Server service. For more information, see Stopping, starting or restarting vCenter services (1003895).