Rsyslog service can not start after update to rsyslog-8.2106.0-8.5.2.x86_64
This document (000020705) is provided subject to the disclaimer at the end of this document.
Environment
SUSE Linux Enterprise Server for SAP Applications 12 SP5
Situation
# zypper in -t patch SUSE-SLE-SERVER-12-SP5-2022-2314 Refreshing service 'SUSE_Linux_Enterprise_Server_x86_64'. Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW patch is going to be installed: SUSE-SLE-SERVER-12-SP5-2022-2314 The following package is going to be upgraded: rsyslog 1 package to upgrade. Overall download size: 746.3 KiB. Already cached: 0 B. After the operation, additional 396.9 KiB will be used. Continue? [y/n/...? shows all options] (y): Retrieving package rsyslog-8.2106.0-8.5.2.x86_64 (1/1), 746.3 KiB ( 2.3 MiB unpacked) Retrieving: rsyslog-8.2106.0-8.5.2.x86_64.rpm ....................[done] Checking for file conflicts: .....................................[done] (1/1) Installing: rsyslog-8.2106.0-8.5.2.x86_64 ..................[done] Additional rpm output: Updating /etc/sysconfig/syslog... Job for rsyslog.service failed because the control process exited with error code. See "systemctl status rsyslog.service" and "journalctl -xe" for details.The service status shows rsyslog.service in a failed state.
# systemctl status rsyslog.service ● rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2022-07-21 21:09:05 CST; 1min 13s ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 6596 ExecStart=/usr/sbin/rsyslogd -n -iNONE $RSYSLOGD_PARAMS (code=exited, status=127) Process: 6591 ExecStartPre=/usr/sbin/rsyslog-service-prepare (code=exited, status=0/SUCCESS) Main PID: 6596 (code=exited, status=127) Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Unit entered failed state. Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Failed with result 'exit-code'. Jul 21 21:09:05 12sp5 systemd[1]: Starting System Logging Service... Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Main process exited, code=exited, status=127/n/a Jul 21 21:09:05 12sp5 systemd[1]: Failed to start System Logging Service. Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Unit entered failed state. Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Failed with result 'exit-code'. Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Start request repeated too quickly. Jul 21 21:09:05 12sp5 systemd[1]: Failed to start System Logging Service. Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Failed with result 'start-limit'.The journal log shows an error.
# journalctl -xe Jul 21 21:09:05 12sp5 systemd[1]: rsyslog.service: Main process exited, code=exited, status=127 Jul 21 21:09:05 12sp5 systemd[1]: Failed to start System Logging Service. -- Subject: Unit rsyslog.service has failedWhen attempting to run the rsyslogd daemon, the following error is observed.
# /usr/sbin/rsyslogd /usr/sbin/rsyslogd: symbol lookup error: /usr/sbin/rsyslogd: undefined symbol: fjson_global_do_case_sensitive_comparison
Resolution
# zypper install -t patch SUSE-SLE-SERVER-12-SP5-2022-2028
Cause
Additional Information
Disclaimer
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020705
- Creation Date: 21-Jul-2022
- Modified Date:15-Aug-2022
-
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com