Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Increase defaults of systemd-coredump for ProcessSizeMax and ExternalSizeMax #22076

Closed
kgibm opened this issue Jan 10, 2022 · 2 comments · Fixed by #22448
Closed

Increase defaults of systemd-coredump for ProcessSizeMax and ExternalSizeMax #22076

kgibm opened this issue Jan 10, 2022 · 2 comments · Fixed by #22448
Labels
coredump RFE 🎁 Request for Enhancement, i.e. a feature request
Milestone
v251

Comments

@kgibm
Copy link

kgibm commented Jan 10, 2022

Is your feature request related to a problem? Please describe.

The default values of ProcessSizeMax and ExternalSizeMax for systemd-coredump are 2GB. We support Java customers who often run processes that are much larger. Truncated core dumps cause a lot of extra back-and-forth to have them understand and tune /etc/systemd/coredump.conf and then they have to experience another production outage to reproduce the problem to get an untruncated core dump.

Describe the solution you'd like

Increase the default ProcessSizeMax and ExternalSizeMax. As far as what might be a good new default, I think that's open to debate. In my opinion, I suggest the default to be equal to MaxUse.

Describe alternatives you've considered

Many support engineers have just taken the simpler approach of disabling systemd-coredump; for example:

We know that settings like this will work:
/proc/sys/kernel/core_pattern = core
** "core" with no other options

The systemd version you checked that didn't have the feature you are asking for

Most recently released upstream version
@yuwata yuwata added coredump RFE 🎁 Request for Enhancement, i.e. a feature request labels Jan 12, 2022
@poettering poettering added this to the v251 milestone Jan 28, 2022
@keszybz
Copy link
Member

keszybz commented Feb 7, 2022

@bluca you had some idea how to process core dumps without saving them to disk first. If we had that, that'd be beneficial on many fronts. We could unset ProcessSizeMax then, no?

@bluca
Copy link
Member

bluca commented Feb 7, 2022

Yeah I had a patchset to process corefiles directly from memory, but it was changed on review, see discussion at: #19166 (comment)

poettering added a commit to poettering/systemd that referenced this issue Feb 8, 2022
@poettering
coredump: raise the coredump save size on 64bit systems to 32G (and l…
e677041 
…ower it to 1G on 32bit systems)

Apparently 2G is too low for various real-life systems. But raising it
universally above 2^32 sounds wrong to me, since that makes no sense on
32bit systems, that we still support.

Hence, let's raise the limit to 32G on 64bit systems, and *lower* it to
1G on 32bit systems.

32G is 4 orders of magnitude higher then the old settings. Let's hope
that's enough for now. Should this not be enough we can raise it
further.

Fixes: systemd#22076
@poettering poettering linked a pull request Feb 8, 2022 that will close this issue
coredump: raise limits #22448
Merged
@kgibm kgibm mentioned this issue Nov 25, 2022
Closed
@kgibm kgibm mentioned this issue Dec 28, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
coredump RFE 🎁 Request for Enhancement, i.e. a feature request
Milestone
v251
Development

Successfully merging a pull request may close this issue.

coredump: raise limits poettering/systemd
5 participants
@keszybz @bluca @poettering @kgibm @yuwata