VMware HA Log is filling up the File System

Details

The VMware High Availability log file located /opt/lgtoaam512/log/rule/vmwareclustermanager.tracereaches 1-2 GB in size.

Solution

You must create an additional job in logrotate to control the size of the log.

As user root on the ESX Host:

  1. Backup the /etc/logrotate.conf file.

    cp /etc/logrotate.conf /etc/backup-logrotate.conf

  2. Add the following lines to the end of the /etc/logrotate.conf file:

    /opt/LGTOaam512/log/rule/VMWareClusterManager.trace { rotate 2 daily
    size=200M notifempty compress }

  3. Save the file.

This change keeps the file from growing to large. It works by using the logrotate cron job to backup and compress the old version of the log. It restricts the number of logs to 2. It is done on a daily basis and when the file is not zero size and when the size grows above 200 MegaBytes.

Keywords

HA log, huge log, log too large, vmwareclustermanager.trace, logrotate
Based on VMware KB 1003148
  • 0 Uživatelům pomohlo
Byla tato odpověď nápomocná?

Související články

Hardware and firmware requirements for 64-bit guest operating systems

PurposeThis article explains the host machine hardware and firmware requirements for installing...

Logging in to the vCenter Server 5.0 Web Client fails with the error: unable to connect to vCenter Inventory Service

DetailsAfter upgrading from vCenter Server 4.1 to 5.0, you experience these symptoms:Cannot log...

Multiple network entries in vCenter Server 5.0.x after migrating virtual machines from a virtual switch to a virtual distributed switch

SymptomsAfter migrating virtual machines from a virtual switch to a virtual Distributed...

Minimum requirements for the VMware vCenter Server 5.x Appliance

PurposeIf you are using the VMware vCenter Server Appliance, beginning with vSphere 5.0 you can...