NIP: container restart loop

Alert: NipContainerRestartLoop · Severity: Warning

What this means

A compose service container restarted more than twice in 10 minutes (cAdvisor container_start_time_seconds changes).

Business impact

• Intermittent transfer failures during each restart.
• Often crash-loop from bad config, OOM, or missing dependency.

Confirm

docker ps -a --format 'table {{.Names}}\t{{.Status}}'
docker events --since 30m --filter event=restart
docker logs <container> --tail 150

Fix

1. Read logs for exit reason (DB connection, import error, OOM).
2. If OOM → container OOM.
3. If dependency — ensure db and redis healthy first.
4. docker compose -f docker-compose.deploy.yml up -d <service> once root cause addressed.
5. Do not restart in a tight loop without fixing cause.

Escalate if

Web or db in restart loop >15 minutes.