Fix transient health checks and avoid unnecessary recovery
This commit is contained in:
+10
-2
@@ -106,10 +106,18 @@ The health observer (the watchdog) scans once per minute. Three observations ove
|
||||
at least two minutes are required before an automatic health restart; starting or
|
||||
restarting containers get five minutes. Unknown Komodo responses are observations,
|
||||
not proof of a stopped container. Repeated manual checks do not accelerate this
|
||||
window.
|
||||
window. A successful routine or manual game-status probe between scans resets
|
||||
the failure streak. Missing RCON configuration, unresolved ports, and invalid
|
||||
replies remain diagnostic findings and cannot authorize health recovery.
|
||||
|
||||
A health finding gets one restart, then one rebuild if recovery fails after five
|
||||
minutes. Escalation transfers only that finding's restart slot. A failed rebuild
|
||||
minutes and fresh health checks still justify recovery. If current container and
|
||||
game checks succeed before an automatic health restart or rebuild is submitted,
|
||||
the obsolete operation is cancelled and the finding is resolved. Unknown health
|
||||
holds recovery for another check. Drift repairs and requested lifecycle operations
|
||||
retain their own eligibility rules.
|
||||
|
||||
Escalation transfers only that finding's restart slot. A failed rebuild
|
||||
requires operator attention. **Rebuild deletes all instance files** and uses the
|
||||
latest promoted setup, the same server identity and port, and the saved server key.
|
||||
Missing keys block teardown. Submitted rebuild verification continues while paused.
|
||||
|
||||
Reference in New Issue
Block a user