Unfortunately the fix did not help. Output in the journal now has an extra line about creating a slice.
:~$ sudo journalctl --file /run/log/journal/<xxx>/system.journal Jul 13 02:29:08 COBPTTDev kernel: asterisk[1570]: segfault at 3000000028 ip 00007f4961158d16 sp 00007f48d84e8a38 error 4 in libc-2.23.so[7f49610ce000+1c0000] Jul 13 02:29:08 COBPTTDev systemd[1]: Created slice system-systemd\x2dcoredump.slice. Jul 13 02:29:08 COBPTTDev systemd[1]: Started Process Core Dump (PID 1607/UID 0). Jul 13 02:29:08 COBPTTDev systemd-coredump[1608]: Coredump file descriptor missing. Likewise the coredump list is empty :~$ sudo coredumpctl list /usr/sbin/asterisk No coredumps found. (asterisk is the Ubuntu package in Xenial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1602256 Title: sometimes "systemd-coredump[<PID>]: Coredump file descriptor missing." is seen, upstream #2984 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: Please include this upstream fix/pull request: coredump: use next_datagram_size_fd instead of ioctl(FIONREAD) #3237 https://github.com/systemd/systemd/pull/3237 Reported as sometimes "systemd-coredump[<PID>]: Coredump file descriptor missing." is seen, upstream #2984 https://github.com/systemd/systemd/issues/2984 Or make a release using systemd tag=v230 :~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 :~$ apt-cache policy systemd systemd: Installed: 229-4ubuntu6 Candidate: 229-4ubuntu6 Version table: *** 229-4ubuntu6 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages SRU INFORMATION --------------- This only affects systemd-coredump which we don't use in Ubuntu by default (we use Apport), so the regression potential is very low. There is no straightforward reproducer for this (see upstream bug report: https://github.com/systemd/systemd/issues/2984). But our systemd package has integration tests for coredump: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/tests/boot-and-services?h=ubuntu-xenial#n436 Thus if the updated package still succeeds its autopkgtests, this should provide sufficient regression testing for this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1602256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
