Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40737 - [systemd] systemd-coredump Cannot save cores larger than max journal entry size (767MiB)

Attached to Project: Arch Linux
Opened by Jeff Mickey (codemac) - Friday, 06 June 2014, 18:19 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 14 June 2014, 13:03 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

https://bbs.archlinux.org/viewtopic.php?id=180899

Read through this thread, but the summary is as follows:

systemd takes over corefile writing using the pipe syntax for the core_pattern the kernel uses.

% cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %p %u %g %s %t %e

This systemd-coredump programs writes out cores to the journal. The acceptable size of a core is less than or equal to the max entry size in the journal (767 MiB).

/* Make sure to not make this larger than the maximum journal entry
* size. See ENTRY_SIZE_MAX in journald-native.c. */
#define COREDUMP_MAX (767*1024*1024u)
assert_cc(COREDUMP_MAX <= ENTRY_SIZE_MAX);


This *ignores* ulimit settings per pid, and then procedes to not save *any* of the core, not even a part of one. This is broken, and should be disabled at least until they figure out how to save cores of arbitrary sizes.

I filed this as high severity - because it is for me.. but there is a working work around.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 14 June 2014, 13:03 GMT
Reason for closing:  Implemented
Additional comments about closing:  systemd 214-2
Comment by Dave Reisner (falconindy) - Friday, 06 June 2014, 22:53 GMT
Please file a bug report upstream, if there isn't one already.
Comment by Jeff Mickey (codemac) - Tuesday, 10 June 2014, 22:04 GMT
There are several upstream - and they get little to no response.

Arch should definitely disable usage of this tool until it is considerably more stable.

https://bugs.freedesktop.org/show_bug.cgi?id=62650 - still open
https://bugs.freedesktop.org/show_bug.cgi?id=62501 - "fixed", but now instead of truncating just doesn't save at all
https://bugs.freedesktop.org/show_bug.cgi?id=62043 - executables can't have spaces in their names
https://bugs.freedesktop.org/show_bug.cgi?id=59623 - same dumb "truncation fix" that breaks large coredumps
https://bugs.freedesktop.org/show_bug.cgi?id=55613 - Open since october 2012 with no response
https://bugs.freedesktop.org/show_bug.cgi?id=54288 - cores are unvisible to normal users (need root or adm group access), unfixed since august 2012

PLEASE disable this tool's usage in default archlinux installs. It's seriously broken in many ways.

Loading...