On Fri, Sep 16, 2016 at 11:02:44AM -0600, Chris Murphy wrote: > On Thu, Sep 15, 2016 at 7:05 PM, Zbigniew Jędrzejewski-Szmek > <zbyszek@xxxxxxxxx> wrote: > > 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@xxxxxxxxx> 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. > > None have * So this is the issue really. I guess we should make the output more clear in that case. Please try something as simple as bash -c 'kill -ABRT $$' → this should result in a coredump appearing in /var/lib/systemd/coredump. If it doesn't than maybe you don't have enough free space and systemd-coredump, or something else is wrong. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
