rsyslog failing when installing/upgrading/updating to 6.7U3 GA
Article ID: 320868
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Symptoms:
- rsyslog fails during install/upgrade/update to vSphere 6.7 U3
- In /var/log/vmware/messages you see an error similar to the log entries given below:
2019-10-02T12:06:01.293972+00:00 vcsa01 CROND[28642] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
2019-10-02T21:36:49.453767+00:00 vcsa01 systemd[1] Stopping System Logging Service...
2019-10-02T21:37:01.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)
2019-10-02T21:37:01.420513+00:00 vcsa01 CROND[633] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
2019-10-02T21:38:01.580236+00:00 vcsa01 CROND[909] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
2019-10-02T21:38: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)
2019-10-02T21:38:19.656828+00:00 vcsa01 systemd[1] rsyslog.service: State 'stop-sigterm' timed out. Killing.
2019-10-02T21:38:19.662312+00:00 vcsa01 systemd[1] rsyslog.service: Main process exited, code=killed, status=9/KILL
2019-10-02T21:38:19.663144+00:00 vcsa01 systemd[1] Stopped System Logging Service.
2019-10-02T21:38:19.663358+00:00 vcsa01 systemd[1] rsyslog.service: Unit entered failed state.
2019-10-02T21:38:19.663543+00:00 vcsa01 systemd[1] rsyslog.service: Failed with result 'signal'.
2019-10-02T21:38:19.678286+00:00 vcsa01 systemd[1] Starting System Logging Service...
2019-10-02T21:38:19.714965+00:00 vcsa01 systemd[1] Started System Logging Service.
2019-10-02T21:36:49.453767+00:00 vcsa01 systemd[1] Stopping System Logging Service...
2019-10-02T21:37:01.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)
2019-10-02T21:37:01.420513+00:00 vcsa01 CROND[633] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
2019-10-02T21:38:01.580236+00:00 vcsa01 CROND[909] (root) CMD ( test -x /usr/sbin/vpxd_periodic && /usr/sbin/vpxd_periodic >/dev/null 2>&1)
2019-10-02T21:38: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)
2019-10-02T21:38:19.656828+00:00 vcsa01 systemd[1] rsyslog.service: State 'stop-sigterm' timed out. Killing.
2019-10-02T21:38:19.662312+00:00 vcsa01 systemd[1] rsyslog.service: Main process exited, code=killed, status=9/KILL
2019-10-02T21:38:19.663144+00:00 vcsa01 systemd[1] Stopped System Logging Service.
2019-10-02T21:38:19.663358+00:00 vcsa01 systemd[1] rsyslog.service: Unit entered failed state.
2019-10-02T21:38:19.663543+00:00 vcsa01 systemd[1] rsyslog.service: Failed with result 'signal'.
2019-10-02T21:38:19.678286+00:00 vcsa01 systemd[1] Starting System Logging Service...
2019-10-02T21:38:19.714965+00:00 vcsa01 systemd[1] Started System Logging Service.
Environment
VMware vCenter Server 6.7.x
Cause
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 issue occurs due to rsyslog failing on VMware vCenter 6.7.0 build-14368073 due to an RPM error.
Resolution
This is resolved in vSphere 6.7 U3g, Build 16046470.
Workaround:
To workaround this issue:
Workaround:
To workaround this issue:
- Login to the vCSA Appliance as root user.
- cd /usr/bin
- Run the commands : systemctl stop syslog
- rm /var/run/rsyslogd.pid
- systemctl start syslog
Feedback
Yes
No
Powered by
