This question already has an answer here:

Generating coredumps used to work fine, but after switching over to systemd, I only see the message

Aborted (core dumped)

but no core file is generated. Has it something to do with systemd?

(Background: My original question can be found here. Thanks schaiba for finding the solution. I provide this Q&A, so others can find the solution easier if they already know that it is a systemd issue.)

marked as duplicate by Caleb, goldilocks, Renan, jasonwryan, George M Feb 18 '13 at 1:30

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

up vote 8 down vote accepted

The /proc/sys/ kernel settings are manged by sysctl(8), the system defaults live in /usr/lib/sysctl.d/, overridden by /etc/sysctl.conf or /etc/sysctl.d/. They define the name of the core files and such. Not their writing (unless the kernel is configured to allow core dumps from SUID binaries). The writing is controlled by ulimit(1), i.e., ulimit -c unlimited gives no limits. Under systemd(1) core files generated by stuff under its control are written to the journal, can be retrieved by coredumpctl(1). Normal user stuff is unchanged.

systemd's systemd-sysctl.service just runs sysctl at the proper point of boot, and handles rerunning on changes.

Per default, systemd writes coredumps to the journal. coredumpctl list lists the missing coredumps.

The files are stored in /var/lib/systemd/coredump. Use coredumpctl dump to get access to the core files.

For instance, if the PID was 10666, you can use

coredumpctl dump 10666 --output /tmp/core.10666

Not related to systemd, but if it is still not working, make sure that the coredump limit is turned off:

# ulimit -c unlimited

Also verify that you can write to the working directory.

  • 1
    Note that the file one has to overwrite is now 50-coredump.conf. – JonnyJD Aug 10 '14 at 11:11

Not the answer you're looking for? Browse other questions tagged or ask your own question.