Bug 2327296 - rpcbind is terminated with ABRT in the initrd
Summary: rpcbind is terminated with ABRT in the initrd
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: rpcbind
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-19 14:10 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2025-02-26 13:17 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Zbigniew Jędrzejewski-Szmek 2024-11-19 14:10:17 UTC 
I'm looking at the logs for https://bugzilla.redhat.com/show_bug.cgi?id=2325780, and noticed the following in the logs from the initrd:

rpcbind[918]: cannot get information for <some garbled bytes>
systemd-coredump[925]: Process 919 (rpcbind) of user 32 terminated abnormally with signal 6/ABRT, processing...
systemd-coredump[925]: Failed to connect to coredump service: No such file or directory
rpc.statd[923]: Version 2.8.1 starting

So we don't get a backtrace or any additional details. But this seems entirely repeatable, I get that message (with slightly different numbers) every time. Looks like uninitialized memory.


Reproducible: Always
Comment 1 Aoife Moloney 2025-02-26 13:17:08 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.
Note You need to log in before you can comment on or make changes to this bug.