Bug 1843566

Summary:	journalctl with --follow option results in segfault
Product:	[Fedora] Fedora	Reporter:	Daniel Berger <dberger>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	32	CC:	fsumsal, lnykryn, msekleta, ssahani, s, systemd-maint, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-245.7-1.fc32	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-30 18:56:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Berger 2020-06-03 14:50:45 UTC

Description of problem:

The --follow option to journalctl causes a segfault.


Version-Release number of selected component (if applicable):

systemd 245 (v245.4-1.fc32)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified


How reproducible:

Always


Steps to Reproduce:

journalctl --file=/var/log/journal/*/* --lines=300 --output=json --all --follow

Actual results:

Segfault


Expected results:

Standard journalctl output


Additional info:

https://github.com/systemd/systemd/pull/15544

Comment 1 Zbigniew Jędrzejewski-Szmek 2020-06-03 14:52:32 UTC

Coredump? Details?

Comment 2 Frantisek Sumsal 2020-06-03 14:53:56 UTC

I have a sneaking suspicion this is going to be the same issue as in https://github.com/systemd/systemd/issues/15528 fixed by https://github.com/systemd/systemd/pull/15544.

Comment 3 Daniel Berger 2020-06-03 14:56:37 UTC

Oof, this interface. Anyway, here's what I submitted, but which BZ mysteriously dropped:

Description of problem:

The --follow option to journalctl causes a segfault.

Version-Release number of selected component:

systemd 245 (v245.4-1.fc32)
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified

How reproducible:

Always.

Steps to reproduce:

journalctl --file=/var/log/journal/*/* --lines=300 --output=json --all --follow

Actual results:

segfault

Expected results:

Standard journalctl output

Additional Info:

https://github.com/systemd/systemd/pull/15544

Comment 4 Zbigniew Jędrzejewski-Szmek 2020-06-03 15:44:57 UTC

Thank you both. It seems I missed this commit when cherry-picking patches for -stable. Will go out in the next batch.

Comment 5 Daniel Berger 2020-06-03 16:35:55 UTC

Updated the original post (I only just discovered the edit option). Sorry about that.

Anyway, thanks!

Comment 6 Fedora Update System 2020-07-27 09:52:03 UTC

FEDORA-2020-2faf839786 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2faf839786

Comment 7 Fedora Update System 2020-07-28 15:19:18 UTC

FEDORA-2020-2faf839786 has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2faf839786`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2faf839786

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2020-07-30 18:56:11 UTC

FEDORA-2020-2faf839786 has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.