On Thu, Sep 15, 2016 at 08:52:03AM -0600, Chris Murphy wrote:
On Thu, Sep 15, 2016 at 8:17 AM, Michael Catanzaro
<mcatanzaro(a)gnome.org> wrote:
> Hi,
>
> Something between F23 and F24 broke coredumpctl in Fedora. It's still
> broken. Appears to be an SELinux bug. It's reported as [1]. I want
> coredumpctl to be enabled by default in F26 as a F26 feature, but I can
> hardly go ahead and propose that while it's still broken. It would be
> great if the SELinux developers could look into the issue. systemd
> developers have been responsive and already left several comments in
> the bug, but I've failed to get the attention of SELinux folks thus
> far.
I think that's only part of the problem. I regularly get: is not a
core dump: File format not recognized
I asked about it on systemd list and there's no reply. And very often
now I get this: More than one entry matches, ignoring rest.
I replied to that other
mail, but in general it seems that you're
hitting some bug which prevent systemd-coredump from reading and saving
a proper coredump. Or maybe you are looking at log entries for which
the coredump is already gone? Try on of the ones which have '*'
in the "present" column.
Please have a look at the files in /var/lib/systemd/coredump.
Those should be normal (possibly lz4-compressed) coredumps, and
gdb should be able to read them without any coredumpctl interaction.
I get the 'more than one entry matches'
That is
harmless, coredumpctl should just use last matching entry.
There's also no command to clean things up.
You can just do
rm /var/lib/systemd/coredump/* or something time
based.
And my favorite:
Refusing to dump core to tty.
OK, so that's a bug: coredumpctl prints that
message before checking
whether the coredump is accessible:
I filed
https://github.com/systemd/systemd/issues/4161.
Zbyszek