event & log

Due to VMware High Availability issues, one or more virtual machines have been attempting to power on repeatedly, generating new vmware.log files over an extended period of time. To resolve this issue, remove the extraneous vmware.log files.

Caution: This article provides steps that require you to permanently delete files from your datastore. Use extreme caution when performing these steps.

Disable and re-enable VMware HA on the cluster to stop the VMware HA issue from continuing further. This can be verified as failover errors stop appearing on the Events tab of affected virtual machines in VirtualCenter.

At the service console, change directory to the folder of a virtual machine that contains extraneous amounts of vmware-x.logs.

Note: File access is delayed, so commands to search all datastores for log files return too many files or fails. Proceed through affected virtual machines, one by one.

To get a count on the number of vmware-x.log files in the folder, run:

1. ls *.log | wc -l

To remove the logs, run:

1. rm -f vmware-*.log

This deletes all log files, unless there are too many arguments. That is, too many files for the rm command to handle. In this case, try deleting all files beginning with vmware-1:

1. rm -f vmware-1*.log

If there are tens of thousands of files, there may be over a thousand beginning with 1, so again too many arguments. You must be more specific:

1. rm -f vmware-10*.log
2. rm -f vmware-11*.log
3. rm -f vmware-12*.log

If necessary, continue to narrow down the command's deletion candidates until you reach an acceptable file count.

Keep removing the log files until only vmware.log remains. Repeat for any other virtual machines affected.