Vmafdd.log Too Big Jun 2026

Run the following command as cited by Broadcom Knowledge Base :

If the issue persists after NTP sync, reissue the machine certificate.

To resolve this properly, you must align the service's logging path with the rotation configuration. Ensure you have a fresh vCenter backup or snapshot before making changes. vmafdd.log too big

/opt/likewise/bin/lwregshell set_value "[HKEY_THIS_MACHINE\Services\vmafd\Parameters]" "LogFile" "/var/log/vmware/vmafdd/vmafdd.log" ``` Use code with caution. Restart all vCenter services to apply the change:

/var/log/vmware/vmafd/vmafdd.log

Under normal conditions, this file rotates and stays under 10–50 MB. However, under specific failure conditions, it explodes in size literally by the gigabyte per hour.

vmafdd must communicate with the vCenter’s Secure Token Service (typically on port 443). If there is a firewall rule blocking traffic, a DNS resolution failure, or a temporary network partition, the daemon will log connection timeout errors repeatedly until connectivity is restored. Run the following command as cited by Broadcom

mv /var/log/vmafdd.log /var/log/vmafdd.log.corrupt touch /var/log/vmafdd.log chmod 644 /var/log/vmafdd.log