Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34734 - [systemd] systemd-coredumpctl cannot be used to dump core files
Attached to Project:
Arch Linux
Opened by Jason Vas Dias (JVD66) - Thursday, 11 April 2013, 17:04 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 May 2013, 15:24 GMT
Opened by Jason Vas Dias (JVD66) - Thursday, 11 April 2013, 17:04 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 22 May 2013, 15:24 GMT
|
DetailsAdditional info: x86_64 multilib ArchLinux distribution up-to-date as of 2013-04-11
* package version(s) systemd-200 systemd-201 * config and/or log files etc. Steps to reproduce: 1. list coredumps (occuring from attempt to run ftpd with xinetd): $ systemd-coredumpctl list 15760 TIME PID UID GID SIG EXE Thu 2013-04-11 16:18:28 GMT 15760 0 0 11 /usr/libexec/ftpd 2. Attempt to extract one: $ systemd-coredumpctl -o core.ftpd.15760 15760 TIME PID UID GID SIG EXE Thu 2013-04-11 16:18:28 GMT 15760 0 0 11 /usr/libexec/ftpd More than one entry matches, ignoring rest. There is no output to the core.ftpd.15760 output file. The systemd-coredumpctl from systemd-200 evidently cannot be used to dump core files, and the build of systemd-201 fails with coredumps during the test phase: $ gunzip < ~/downloads/systemd-201-1.src.tar.gz && cd systemd && makepkg ... PASS: test-strxcpyx ./build-aux/test-driver: line 95: 23850 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-unit-name ... PASS: test-replace-var ./build-aux/test-driver: line 95: 23977 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-sched-prio ... ==> ERROR: A failure occurred in check(). Aborting... My impressions so far of systemd is that it is overcomplex, highly non-intuitive and non-compliant with existing practices, a nightmare to configure, buggy and of insufficient code quality for use outside its test and development environment, an impression that is confirmed by the inability of the latest source code for it to pass its own test suite. Please bring back initscripts or move to upstart ! Meanwhile, can anyone please suggest a way of recovering a core dump from the systemd-journald binary database ? Thanks, Jason |
This task depends upon
Closed by Dave Reisner (falconindy)
Wednesday, 22 May 2013, 15:24 GMT
Reason for closing: Upstream
Additional comments about closing: Nothing to do here. Upstream is already working on a way to "log" coredumps to disk as well.
Wednesday, 22 May 2013, 15:24 GMT
Reason for closing: Upstream
Additional comments about closing: Nothing to do here. Upstream is already working on a way to "log" coredumps to disk as well.
If you want to use upstart, Ubuntu awaits you. If you'd rather pretend it's 1992 all over again, Slackware exists. I wish you luck.
> Meanwhile, can anyone please suggest a way of recovering a core dump from the systemd-journald binary database ?
You could simply disable logging of coredumps to the journal (by masking the sysctl.d entry in /usr/lib/sysctl.conf) and let them be written to disk instead.