Vmafdd.log Too — Big

There are four primary reasons why this log file exceeds safe limits.

| Order | Action | Command / Method | |-------|--------|------------------| | 1 | Stop log growth | /etc/init.d/vmafdd stop | | 2 | Clear existing log | truncate -s 0 /var/log/vmafdd.log | | 3 | Check time sync | esxcli system time get vs date on vCenter | | 4 | Restart service | /etc/init.d/vmafdd start | | 5 | Renew certificates | vSphere UI or generate-certificates | | 6 | Harden log rotation | Edit /etc/vmware/logrotate.conf | | 7 | Set monitoring alert | vCenter Alarm or custom script | vmafdd.log too big

Using vSphere Client:

Log in to your VCSA via SSH and switch to the BASH shell. Run the following command to check which files are consuming the most space: du -ah /storage/log/ | sort -h -r | head -n 20 vmafdd.log appears at the top with a massive size, proceed to the fix. 2. Update the Registry Path There are four primary reasons why this log

Apply the changes by restarting all vCenter services. Note that this will briefly interrupt access to the vSphere Client. ```bash service-control --stop --all && service-control --start --all ``` ## Long-term Resolution This bug is officially resolved **vCenter Server proceed to the fix.