Bug 1477233

Summary: Huge coredumps os atomic-openshift-api.service when it restarts
Product: OpenShift Online Reporter: Gabor Burges <gburges>
Component: MasterAssignee: Dan Mace <dmace>
Status: CLOSED DUPLICATE QA Contact: Wang Haoran <haowang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.xCC: aos-bugs, bmorriso, decarr, dmace, gburges, jokerman, mfojtik, mmccomas, mstaeble, sjenning, xtian
Target Milestone: ---Keywords: OnlineStarter, OpsBlocker
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-09-15 19:36:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gabor Burges 2017-08-01 14:18:15 UTC 
Description of problem:

When the api service gets in a bad state (not normally stopped) and restarts it writes a huge core.<#####> file in /var/lib/origin/

This is especially problematic on starter-us-east-1 because the core file takes up more than 11GB of the 16GB of the filesystem

Moving said core file out of the dir kills the process again, generating another huge core file

Version-Release number of selected component (if applicable):
oc v3.6.170
kubernetes v1.6.1+5115d708d7
features: Basic-Auth GSSAPI Kerberos SPNEGO

openshift v3.6.170
kubernetes v1.6.1+5115d708d7


How reproducible:
get the atomic-openshift-api.service in a bad state 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1277329
Comment 1 Seth Jennings 2017-08-08 22:38:45 UTC 
What is the output of "ulimit -c"?

If "unlimited" try adding the following line to /etc/security/limits.conf:

* hard core 0

Setting coredump file size limits would really need to be addressed at the installer level.
Comment 3 Matthew Staebler 2017-08-16 21:14:18 UTC 
Need confirmation from the reporter that setting the coredump file size limits resolves the issue.

See Comment #1.
Comment 8 Red Hat Bugzilla 2023-09-14 04:01:56 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days