diff options
| author | Matthew Barth <msbarth@us.ibm.com> | 2020-08-07 17:35:20 +0300 |
|---|---|---|
| committer | Andrew Geissler <geissonator@yahoo.com> | 2020-09-17 00:35:31 +0300 |
| commit | b3da8c94cda94c18918629ed0df7a9508ca9965c (patch) | |
| tree | ba1facb20e666a0710659b00aa54e38f6be934f3 /meta-ibm/recipes-phosphor/fans | |
| parent | b2255dccf198e765e836e61d115b3d64d4a545a7 (diff) | |
| download | openbmc-b3da8c94cda94c18918629ed0df7a9508ca9965c.tar.xz | |
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
(From meta-ibm rev: b8a65368cb39d6d82c4b025b25fdbe868dbbfe89)
Change-Id: Ibcb35028e8dbc67d7df70dfeee25d098e6041fe8
Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Diffstat (limited to 'meta-ibm/recipes-phosphor/fans')
| -rw-r--r-- | meta-ibm/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/meta-ibm/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf b/meta-ibm/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf index e72de888f..38a37cbd1 100644 --- a/meta-ibm/recipes-phosphor/fans/phosphor-fan/fan-watchdog-monitor.conf +++ b/meta-ibm/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 |