Hello everyone, I started using OpenSUSE Tumbleweed a few months ago, and I’ve been very happy with it.
Yesterday, however, during the rpm upgrade, I do it weekly, I encountered this problem:
After updating with zypper upgrade:
openSUSE Tumbleweed
20260712-0 → 20260722-0
and subsequent installation of rsyslog-8.2502.0-8.1.x86_64.rpm
At end of work zipper update write:
Output script %transfiletriggerin(systemd-259.5-1.2.x86_64):
Job for rsyslog.service failed because a fatal signal was delivered causing the control process to dump core.
See “systemctl status rsyslog.service” and “journalctl -xeu rsyslog.service” for details.
error: lua script failed: [string “%transfiletriggerin(systemd-259.5-1.2.x86_64)…”]:5: exit code
Error from %transfiletriggerin(systemd-259.5-1.2.x86_64)
…
Output script %transfiletriggerin(info-7.3-1.4.x86_64):
rsyslog.service no longer works:
c_mani_stw0@Mother:~> sudo systemctl restart rsyslog
Job for rsyslog.service failed because a fatal signal was delivered, causing the control process to dump core.
See “systemctl status rsyslog.service” and “journalctl -xeu rsyslog.service” for details.
c_mani_stw0@Mother:~> systemctl status rsyslog
× rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; preset: enabled)
Active: failed (Result: core-dump) since Sat 2026-07-25 12:49:50 CEST; 2s ago
Invocation: 734bfd49647b41abb774a956e44404d2
TriggeredBy: × syslog.socket
Docs: man:rsyslogd(8)
http://www.rsyslog.com/doc/
Process: 6930 ExecStartPre=/usr/sbin/rsyslog-service-prepare (code=exited, status=0/SUCCESS)
Process: 6933 ExecStart=/usr/sbin/rsyslogd -n -iNONE $RSYSLOGD_PARAMS (code=dumped, signal=SEGV)
Main PID: 6933 (code=dumped, signal=SEGV)
CPU: 40ms
c_mani_stw0@Mother:~>
c_mani_stw0@Mother:~> sudo journalctl -xeu rsyslog.service
An ExecStart process belonging to the rsyslog.service unit has exited.
The process’s exit code is ‘dumped’ and it exited with 11.
Jul 25 13:24:27 Mother.Nostromo.CMani.net systemd[1]: rsyslog.service: Failed with result ‘core-dump’.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unit rsyslog.service entered ‘failed’ state with ‘core-dump’ result.
Jul 25 13:24:27 Mother.Nostromo.CMani.net systemd[1]: Failed to start System Logging Service.
Subject: Unit rsyslog.service failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unit rsyslog.service failed.
The result has failed.
Jul 25 13:24:28 Mother.Nostromo.CMani.net systemd[1]: rsyslog.service: Scheduled restart job, restart counter is at 5.
Subject: Automatic restart of a unit has been scheduled.
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Automatic restart of the unit rsyslog.service has been scheduled, as a result
of the settings configured in Restart=.
Jul 25 13:24:28 Mother.Nostromo.CMani.net systemd[1]: rsyslog.service: Start request repeated too quickly.
Jul 25 13:24:28 Mother.Nostromo.CMani.net systemd[1]: rsyslog.service: Failed with result ‘core-dump’.
Subject: Unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Unit rsyslog.service entered ‘failed’ state with ‘core-dump’ result.
Jul 25 13:24:28 Mother.Nostromo.CMani.net systemd[1]: Failed to start System Logging Service.
Subject: The rsyslog.service unit failed
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
The rsyslog.service unit failed.
The result is failed.
c_mani_stw0@Mother:~>
I tried downgrading to rsyslog-8.2502.0-6.5.x86_64.rpm, but the problem persists.
Has anyone had the same problem or have any ideas on how to fix it?
Thanks
