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
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.
Need confirmation from the reporter that setting the coredump file size limits resolves the issue. See Comment #1.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days