When generating a log bundle in a highly utilized vCenter with multiple vSAN clusters, the vCenter log bundle takes upwards of 45 minutes to generate. Log bundle does generate successfully after the long wait.
VMware vCenter 8.x
This can occur due to the transfer of large amounts of vSAN data. Environmental factors also may slow collection as well during pulling of vSAN health service logs.
The action.log file of the generated log bundle will show the following:
[YYYY-MM-DDTHH:MM:SS] run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT python /usr/lib/vmware-vpx/vsan-health/vsan-vc-health-status.py cluster-health (/etc/vmware/vm-support/vsan-health.mfx) took 165.000 sec
[YYYY-MM-DDTHH:MM:SS] run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT python /usr/lib/vmware-vpx/vsan-health/vsan-vc-health-status.py rvc-basic-support-information (/etc/vmware/vm-support/vsan-health.mfx) took 832.000 sec
Note: Since log bundle generation does eventually complete, it is recommended that no actions be taken to resolve this. If log bundle generation time is an issue in the environment, then the following changes may be made to speed up log collection.
vc-support -e 'VirtualAppliance:VsanHealth VirtualAppliance:VsanHealthService'
/etc/vmware/vm-support/vsan-health.mfx
run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT=600 $VMWARE_PYTHON_HOME/python $VMWARE_CIS_HOME/vsan-health/vsan-vc-health-status.py rvc-basic-support-information
run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT=600 $VMWARE_PYTHON_HOME/python $VMWARE_CIS_HOME/vsan-health/vsan-vc-health-status.py cluster-health
run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT=600 $VMWARE_PYTHON_HOME/python $VMWARE_CIS_HOME/vsan-health/vsan-vc-health-status.py other-type-objects