Need to disable apport from setting core_pattern |
||||
Issue descriptionAfter the puppet configuration has been updated (in [0]) to override gce default sysctl settings and configure /proc/sys/kernel/core_pattern, it seems to still get overridden sometimes with apport. Could we get the puppet configuration changed to disable apport (which is a ubuntu crash reporter) in /etc/default/apport by setting "enabled=0" ? [0] https://bugs.chromium.org/p/chromium/issues/detail?id=686652#c12
,
Aug 1 2017
,
Jan 31 2018
FYI, this is still an issue for Dart, for BB we have a workaround, on LUCI we currently don't and will require to solve this in puppet.
,
Feb 1 2018
,
Feb 1 2018
This should only be done on GCE machines right?
,
Feb 4 2018
Is there a specific reason why we would only want that on GCE machines?
AFAIK we want this on all our Ubuntu machines.
Any Ubuntu machine that is affected by this setting (#686652):
classes:
chrome_infra::setup::sysctl:
sysctls: ['kernel.yama.ptrace_scope = 0', 'kernel.core_pattern = core.%p']
should have apport disabled.
whesse@ do you agree?
,
Feb 4 2018
Yes, I agree. Though we should be able to change all the Ubuntu machines to GCE machines (except ARM) pretty soon.
,
Feb 5 2018
,
Feb 5 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/19a3a3ef2de81b30d9ca60055f870e7139bbd705 commit 19a3a3ef2de81b30d9ca60055f870e7139bbd705 Author: Elliott Friedman <friedman@google.com> Date: Mon Feb 05 20:42:22 2018
,
Feb 5 2018
It will be disabled anywhere that core_pattern thing is set now.
,
Apr 6 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/infra/puppet/+/8b131f23f0e06a4cdbd47fab54466fb7ca43ee60 commit 8b131f23f0e06a4cdbd47fab54466fb7ca43ee60 Author: Vadim Shtayura <vadimsh@chromium.org> Date: Fri Apr 06 18:47:25 2018 |
||||
►
Sign in to add a comment |
||||
Comment 1 by whesse@google.com
, Aug 1 2017