Exporting vCenter Server logs take a long time to complete when vCenter Server has multiple vSAN clusters.
The following events are listed in the action.log file within the captured support bundle:
YYYY-MM-DD HH:MM:SS.005867: 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 107.000 sec
YYYY-MM-DD HH:MM:SS506866: run IGNORE_ERROR,IGNORE_MISSING,TIMEOUT python /usr/lib/vmware-vpx/vsan-health/vsan-vc-health-status.py other-type-objects (/etc/vmware/vm-support/vsan-health.mfx) took 27.000 sec
vCenter Server 8.0
The vsan-vc-health-status.py script takes a long time to complete.
When vCenter Server has multiple vSAN clusters, the script can take longer to query health information and this behaviour is expected.
The collected information is included in the vCenter Server bundle by default.
To work around the slow log collection, temporarily skip collecting vsan-health information.
/etc/vmware/vm-support/vsan-health.mfx
cp -v /etc/vmware/vm-support/vsan-health.mfx /etc/vmware/vm-support/vsan-health.mfx.bak
/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
$ mv /etc/vmware/vm-support/vsan-health.mfx /etc/vmware/vm-support/vsan-health.mfx.edit
$ cp -v /etc/vmware/vm-support/vsan-health.mfx.bak /etc/vmware/vm-support/vsan-health.mfx