[Bug] - backport request - systemd journal: signal SIGBUS error

[sugitk]

Describe the bug Systemd journal has a known issue when handling a rotation.

To Reproduce

issue: https://github.com/systemd/systemd/issues/24320 fix: https://github.com/systemd/systemd/pull/29456

It is already merged into systemd v255.

Expected behavior

Screenshots

Desktop (please complete the following information):

Smartphone (please complete the following information):

Additional context

[sugitk]

@stewartsmith

Thank you for catching this issue. Here is a stack trace output observed from the customer's /var/log/messages for your information. Please let me know if you need more information in order to go proceed this issue.

Jan  7 16:29:33 <crit> hostname.example.com systemd-coredump[1474531]:
Process 1646 (rsyslogd) of user 0 dumped core.#012#012
Module liblzma.so.5 from rpm xz-5.2.5-9.amzn2023.0.2.x86_64
#012Module libcap.so.2 from rpm libcap-2.48-2.amzn2023.0.3.x86_64
#012Module libuuid.so.1 from rpm util-linux-2.37.4-1.amzn2023.0.3.x86_64
#012Module libsystemd.so.0 from rpm systemd-252.4-1161.amzn2023.0.3.x86_64
#012Module libfastjson.so.4 from rpm libfastjson-0.99.9-1.amzn2023.0.3.x86_64
#012Module libestr.so.0 from rpm libestr-0.1.11-1.amzn2023.0.2.x86_64
#012Module libz.so.1 from rpm zlib-1.2.11-33.amzn2023.0.4.x86_64

#012Stack trace of thread 1657:
#012#0  0x00007f7c2ec7b2f2 real_journal_next (libsystemd.so.0 + 0x672f2)
#012#1  0x00007f7c2eb9c585 runInput (imjournal.so + 0x4585)
#012#2  0x0000557fae1f2aa3 thrdStarter (rsyslogd + 0x75aa3)
#012#3  0x00007f7c2e89f7f2 start_thread (libc.so.6 + 0x9f7f2)
#012#4  0x00007f7c2e83f450 __clone3 (libc.so.6 + 0x3f450)
#012
#012Stack trace of thread 1646:
#012#0  0x00007f7c2e944ff2 pselect (libc.so.6 + 0x144ff2)
#012#1  0x0000557fae19c1db mainloop (rsyslogd + 0x1f1db)
#012#2  0x0000557fae19517b main (rsyslogd + 0x1817b)
#012#3  0x00007f7c2e83feb0 __libc_start_call_main (libc.so.6 + 0x3feb0)
#012#4  0x00007f7c2e83ff60 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3ff60)
#012#5  0x0000557fae195525 _start (rsyslogd + 0x18525)
#012
#012Stack trace of thread 1720:
#012#0  0x00007f7c2e89c38a __futex_abstimed_wait_common (libc.so.6 + 0x9c38a)
#012#1  0x00007f7c2e89eb90 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x9eb90)
#012#2  0x0000557fae1e2603 wtiWorker (rsyslogd + 0x65603)
#012#3  0x0000557fae1e28a1 wtpWorker (rsyslogd + 0x658a1)
#012#4  0x00007f7c2e89f7f2 start_thread (libc.so.6 + 0x9f7f2)
#012#5  0x00007f7c2e83f450 __clone3 (libc.so.6 + 0x3f450)
#012ELF object binary architecture: AMD x86-64

[nmeyerhans]

I've requested the backport in the upstream systemd-stable project; if they do the backport, we'll pick it up when refreshing to a newer systemd 252.x package in the future. If they can't/won't do the backport themselves, we'll consider carrying a patch for it in our packages, if that ends up being a practical way to address this.

[belimawr]

Hey folks, any chance of this fix being one here? The upstream issue seems pretty stale.

That is an issue for us when trying to read the journal files :/