diff options
| author | Andrew Geissler <geissonator@yahoo.com> | 2018-04-26 21:07:37 +0300 |
|---|---|---|
| committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2018-05-02 19:47:24 +0300 |
| commit | 44e81f2ca57c4ac72aa38887c554c25281ca5b6f (patch) | |
| tree | 41129162726784e752e92a73048b6789a00e911d /meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor | |
| parent | a63de4a4141ba56c185b9886412a669a8be83e0b (diff) | |
| download | openbmc-44e81f2ca57c4ac72aa38887c554c25281ca5b6f.tar.xz | |
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>
Diffstat (limited to 'meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor')
0 files changed, 0 insertions, 0 deletions