uptime-kuma: set restart_policy.delay to 30s
ci/woodpecker/push/deploy Pipeline was successful
ci/woodpecker/cron/renovate Pipeline was successful

Increases the delay before Swarm restarts a failed uptime-kuma task
from the default 5s to 30s. Applied live via `docker service update
--restart-delay 30s` on 2026-07-26; this persists it so it survives
the next stack deploy.

Note: this does not pin the task to a specific node or prevent
cross-node reschedule races against the CephFS-backed SQLite data
dir - it only slows the restart-after-failure loop. See prior
incident notes for the DB corruption root cause discussion.
This commit is contained in:
2026-07-26 17:34:35 -07:00
parent 7dbc6f490e
commit cebc6a0a8f
+2
View File
@@ -66,6 +66,8 @@ services:
max-size: "10m"
max-file: "3"
deploy:
restart_policy:
delay: 30s
labels:
- traefik.enable=true
- traefik.http.routers.uptime.rule=Host(`uptime.${DOMAIN}`)