To be aware of the Rsyslog service failure post upgrade
Symptoms:
Upon verifying the Rsyslog service status as health check post upgrade, below errors are found:
Below log excerpts are from internal lab:
-----------------------------------------------------
root@Testlcm [ ~ ]# systemctl status rsyslog.service
● rsyslog.service - System Logging Service
Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2023-08-09 05:14:05 UTC; 6h ago
Docs: man:rsyslogd(8)
https://www.rsyslog.com/doc/ Main PID: 1002 (code=exited, status=1/FAILURE)
Aug 09 05:14:05 Testlcm.org systemd[1]: Failed to start System Logging Service.
Aug 09 05:14:05 Testlcm.org systemd[1]: rsyslog.service: Service RestartSec=100ms expired, scheduling restart.
Aug 09 05:14:05 Testlcm.org systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 5.
Aug 09 05:14:05 Testlcm.org systemd[1]: Stopped System Logging Service.
Aug 09 05:14:05 Testlcm.org systemd[1]: rsyslog.service: Start request repeated too quickly.
Aug 09 05:14:05 Testlcm.org systemd[1]: rsyslog.service: Failed with result 'exit-code'.