commit | b8a65368cb39d6d82c4b025b25fdbe868dbbfe89 | [log] [tgz] |
---|---|---|
author | Matthew Barth <msbarth@us.ibm.com> | Fri Aug 07 09:35:20 2020 -0500 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Wed Sep 16 20:41:51 2020 +0000 |
tree | 59b85a859c038f472276dc8370518d0c89505f5f | |
parent | 73b735f30bb866b27e05fe6381064e5a9a55977b [diff] |
fans: Update service start limits for fan watchdog It was found that the fan control services were constantly getting restarted due to not failing within the previous start limits. After experimenting with different combinations of limits, using the default values for StartLimitBurst and StartLimitIntervalSec is sufficient. Tested: Changed limits, powered on, watched service fails in journal until fan watchdog monitor started Resolves: https://github.com/openbmc/phosphor-fan-presence/issues/23 Change-Id: I137807dd8c2e09e3a4019a9ad416b0384824ed65 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
diff --git a/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf b/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf index e72de88..38a37cb 100644 --- a/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf +++ b/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf
@@ -1,5 +1,3 @@ [Unit] #These overrides allow the fan watchdog to take over when this service dies OnFailure=fan-watchdog-monitor@%n.service -StartLimitIntervalSec=5 -StartLimitBurst=3