On Fri, Sep 16, 2016 at 11:26 AM, Zbigniew Jędrzejewski-Szmek <zbys...@in.waw.pl> wrote: > On Fri, Sep 16, 2016 at 11:02:44AM -0600, Chris Murphy wrote:
>> 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. $ coredumpctl Fri 2016-09-16 11:59:37 MDT 3343 1000 1000 6 * /usr/bin/bash $ ls -l /var/lib/systemd/coredump total 0 -rw-r-----+ 1 root root 0 Sep 16 11:59 core.bash.1000.7f1dd932c6594cbdae77969bd76125ca.3343.14740487770000000000 journalctl -f Sep 16 11:59:37 f24m audit[3343]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=3343 comm="bash" exe="/usr/bin/bash" sig=6 Sep 16 11:59:37 f24m systemd[1]: Started Process Core Dump (PID 3344/UID 0). Sep 16 11:59:37 f24m audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-3344-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 16 11:59:37 f24m systemd-coredump[3345]: Failed to compress /var/lib/systemd/coredump/.#core.bash.1000.7f1dd932c6594cbdae77969bd76125ca.3343.1474048777000000000000.lz4fb3b07bda3e93e45: Invalid argument Sep 16 11:59:37 f24m systemd-coredump[3345]: Failed to generate stack trace: invalid `Elf' handle Sep 16 11:59:37 f24m systemd-coredump[3345]: Process 3343 (bash) of user 1000 dumped core. Sep 16 11:59:37 f24m audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@1-3344-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 16 11:59:37 f24m abrt-dump-journal-core[884]: Failed to obtain all required information from journald Sep 16 11:59:37 f24m abrt-dump-journal-core[884]: Failed to obtain all required information from journald Sep 16 11:59:37 f24m abrt-server[3356]: Blacklisted package 'bash' Sep 16 11:59:37 f24m abrt-server[3356]: 'post-create' on '/var/spool/abrt/ccpp-2016-09-16-11:59:37.495036-884' exited with 1 Sep 16 11:59:37 f24m abrt-server[3356]: Deleting problem directory '/var/spool/abrt/ccpp-2016-09-16-11:59:37.495036-884' It looks like maybe some 0 length coredump get cleaned up sooner than non-zero ones (?) and that's why the directory is empty. But I know there were a bunch of * items and that directory had items in it, but then some behavior has changed - I just don't know what or when, only that it was within the lifetime of Fedora 24. -- Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org