kb/subsystems/service-lifecycle.md (visibility private wg rozstrzygniecia 6) kb/runbooks/service-operational-recovery.md — Operational Recovery Tresc sekcji nietknieta. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
788 B
788 B
| okf | type | visibility | status | updated | links | |
|---|---|---|---|---|---|---|
| 0.1 | runbook | private | active | 2026-05-11 |
|
Serwisy — operational recovery
Operational Recovery
1. Container Failure
If a service is unhealthy:
- Check
docker compose logs. - Restart:
docker compose restart. - Recreate:
docker compose up -d --force-recreate.
2. Node Failure
If a host node fails:
- Services with
owner_nodematching the failed node must be recovered on a backup node or the node must be restored. - Persistence data must be restored from backups to
/opt/homelab/data/<service>.
3. Dependency Recovery
If a dependency fails:
- Services depending on it might report unhealthy status.
- Recover the dependency first.
- Re-verify dependent services.