This is an informational article regarding a known issue discovered with the ESX Agent Manager (EAM) service and log file rotation.
In vCenter Server 7.0 Update 1 (or newer), a large number of files may be present under the following directory:
This is caused by EAM not having a log file rotation parameter by default, and will leave older files present with no cleanup invoked.
Due to the new functionality of vSphere Clustering Services in 7.0 Update 1, the amount of polling that occurs with EAM causing these log files to generate quickly and can produce a significant quantity of log files.
This issue is resolved in vCenter Server 8.0 GA (build number 20519528) and above.
In VMware vCenter Server 7.0 Update 3 (build number 18700403) the localhost_access.*.log files are only zipped and not deleted.
Workaround:
In vCenter Server 7.0 Update 1 and Update 2
On the vCenter Server shell (or SSH session)
# service-control --stop vmware-eam
# service-control --start vmware-eam
Example screenshot:
In vCenter Server 7.0 Update 3 and later 7.0 release
vCenter Server 7.0 Update 3 has a partial improvement. The localhost_access.*.log files will be compressed as zip, but not removed.
Remove zip files manually if /storage/log is exhausted.
In vCenter Server 8.x
We will still see a number of localhost_access*.zip files and they will be deleted when a combined size of 128MB is reached.
For more information on the vSphere Cluster Service, please refer to the main KB:
vSphere Cluster Services (vCLS) in vSphere 7.0 Update 1 and newer versions
Impact/Risks:
The impact/risk may be that the /storage/log directory fills up, preventing one or more services from functioning. This can lead to instability of vCenter Server.