Symptoms:
YYYY-MM-DDTHH:MM:SS.293972+00:00 vcsa01 CROND[28642] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
YYYY-MM-DDTHH:MM:SS.453767+00:00 vcsa01 systemd[1] Stopping System Logging Service...
YYYY-MM-DDTHH:MM:SS.419600+00:00 vcsa01 CROND[634] (root) CMD (. /etc/profile.d/VMware-visl-integration.sh; /usr/lib/applmgmt/backup_restore/scripts/SchedulerCron.py >>/var/log/vmware/applmgmt/backupSchedulerCron.log 2>&1)
YYYY-MM-DDTHH:MM:SS.420513+00:00 vcsa01 CROND[633] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
YYYY-MM-DDTHH:MM:SS.580236+00:00 vcsa01 CROND[909] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
YYYY-MM-DDTHH:MM:SS:01.581639+00:00 vcsa01 CROND[910] (root) CMD (. /etc/profile.d/VMware-visl-integration.sh; /usr/lib/applmgmt/backup_restore/scripts/SchedulerCron.py >>/var/log/vmware/applmgmt/backupSchedulerCron.log 2>&1)
YYYY-MM-DDTHH:MM:SS.656828+00:00 vcsa01 systemd[1] rsyslog.service: State 'stop-sigterm' timed out. Killing.
YYYY-MM-DDTHH:MM:SS.662312+00:00 vcsa01 systemd[1] rsyslog.service: Main process exited, code=killed, status=9/KILL
YYYY-MM-DDTHH:MM:SS.663144+00:00 vcsa01 systemd[1] Stopped System Logging Service.
YYYY-MM-DDTHH:MM:SS.663358+00:00 vcsa01 systemd[1] rsyslog.service: Unit entered failed state.
YYYY-MM-DDTHH:MM:SS.663543+00:00 vcsa01 systemd[1] rsyslog.service: Failed with result 'signal'.
YYYY-MM-DDTHH:MM:SS.678286+00:00 vcsa01 systemd[1] Starting System Logging Service...
YYYY-MM-DDTHH:MM:SS.714965+00:00 vcsa01 systemd[1] Started System Logging Service.VMware vCenter Server 6.7.x
This is a known issue affecting VMware vCenter 6.7.0 build-14368073 and above.
This issue occurs due to rsyslog failing on VMware vCenter 6.7.0 build-14368073 due to an RPM error.
This is resolved in vSphere 6.7 U3g, Build 16046470.
Workaround:
To workaround this issue: