From d54db34172b06ed5d449fa564ca3d86a5650357f Mon Sep 17 00:00:00 2001 From: Aditya Kali Date: Wed, 21 Sep 2016 10:08:23 -0700 Subject: [PATCH] Reset core_patern on GCI The default core_pattern pipes the core dumps to /sbin/crash_reporter which is more restrictive in saving crash dumps. So for now, set a generic core_pattern that users can work with. --- cluster/gce/gci/configure-helper.sh | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/cluster/gce/gci/configure-helper.sh b/cluster/gce/gci/configure-helper.sh index 4471435548b..b726c8369e1 100644 --- a/cluster/gce/gci/configure-helper.sh +++ b/cluster/gce/gci/configure-helper.sh @@ -25,6 +25,13 @@ set -o errexit set -o nounset set -o pipefail +function setup-os-params { + # Reset core_pattern. On GCI, the default core_pattern pipes the core dumps to + # /sbin/crash_reporter which is more restrictive in saving crash dumps. So for + # now, set a generic core_pattern that users can work with. + echo "core.%e.%p.%t" > /proc/sys/kernel/core_pattern +} + function config-ip-firewall { echo "Configuring IP firewall rules" # The GCI image has host firewall which drop most inbound/forwarded packets. @@ -1176,6 +1183,7 @@ if [[ -n "${KUBE_USER:-}" ]]; then fi fi +setup-os-params config-ip-firewall create-dirs ensure-local-ssds