Runbook · Maxedge

Service down / container restarting

Docker

Symptom

docker ps shows a service Exited or Restarting; dashboard tile red.

Investigate

docker logs the failing container. Common causes: bad config after upload, full disk, corrupted volume after power loss.

Fix

docker compose -f /opt/maxedge/docker-compose.yml ps
docker logs --tail 200 <service>
docker restart <service>
# full stack:
docker compose -f /opt/maxedge/docker-compose.yml up -d

If the crash followed a config change, roll back: Dashboard → Configuration → History → Restore previous.

Steps

docker ps -a — note which container and its exit code.
docker logs --tail 200 <service>. Config parse error → roll back the config.
df -h — full disk kills every service. Prune and restart.
Power loss and a corrupted volume: docker compose … down, move the volume aside, up -d; the store rebuilds from the PLC (history since the crash is lost).
Verify all services Up and the dashboard tiles green.

Not resolved? Escalate to Product Engineering with docker ps -a, the relevant docker logs and the unit's Masterdata link.