Change the StartLimitIntervalSec to 30s
The BMC CPU performance is already challenged. When a service is
failing and a core dump is being generated and collected into a dump,
it's even more challenged. Recent failures have shown situations where
the service does not fail again until 15-20 seconds after the initial
failure which means the default of 10s for this results in the service
being restarted indefinitely. Change this to 30s to only allow a
service to be restarted StartLimitBurst times within a 30s interval
before being put in a fail state.
Testing: Verified that killing an application 3 times within 30 seconds
results in the service being in a fail state (and not restarted).
Resolves openbmc/openbmc#3131
Change-Id: I58c874c1c5b618c147946195af65f42371d683c8
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/common/recipes-core/systemd/systemd/service-restart-policy.conf b/common/recipes-core/systemd/systemd/service-restart-policy.conf
index 8e440a4..0bd049b 100644
--- a/common/recipes-core/systemd/systemd/service-restart-policy.conf
+++ b/common/recipes-core/systemd/systemd/service-restart-policy.conf
@@ -13,8 +13,19 @@
# restarting once does the job or restarting all 5 times does not help
# and we just end up hitting the 5 limit anyway.
#
+# - Change the StartLimitIntervalSec to 30s
+# The BMC CPU performance is already challenged. When a service is
+# failing and a core dump is being generated and collected into a dump,
+# it's even more challenged. Recent failures have shown situations where
+# the service does not fail again until 15-20 seconds after the initial
+# failure which means the default of 10s for this results in the service
+# being restarted indefinitely. Change this to 30s to only allow a service
+# to be restarted StartLimitBurst times within a 30s interval before
+# being put in a permenant fail state.
+#
# See systemd-system.conf(5) for details on the conf files
[Manager]
DefaultRestartSec=1s
DefaultStartLimitBurst=2
+DefaultStartLimitIntervalSec=30s