[DOCS-9057] Recommendations to disable core dumps on production systems Created: 30/Sep/16  Updated: 30/Oct/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Amar Hamzeh Assignee: Kay Kim (Inactive)
Resolution: Won't Do Votes: 0
Labels: bite-sized, docs-prod-notes-cleanup
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 14 weeks, 2 days ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

Currently, only the 3.2 Upgrade Document recommends disabling core dumps in production systems.

Could we also update the Production notes and/or the Operations Checklist to include the recommendation to disable core dumps on production systems?

On the Unix ulimit Settings page there is a sample output (which includes a core limit of 0) which looks like a recommendation but it's not really clear.

This is usually done with ulimit -c 0.

Under Ubuntu, if the sysctl kernal.core_pattern = |/usr/share/apport/apport %p %s %c (which is the default core_pattern) then apport would be triggered and would write a crash report even if core ulimit is set to 0 (documented on apport webpage). In addition to writing the crash report, if a process crashes, it must wait for apport before it can finish exiting, which might take some time.

One way to stop apport from being triggered is to set:

sudo sysctl -w kernel.core_pattern="core.%e.%p.%h.%t"



 Comments   
Comment by Education Bot [ 31/Oct/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:57:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.