fix: give Postgres a 5-minute start_period in both TrueNAS composes
After an unclean shutdown, WAL replay outlasted the 5 x 10 s healthcheck window, so compose marked Postgres unhealthy and refused to start any dependent service. The paper app sat in 'Deploying' on 2026-09-30. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01B3PXXn2tHBzdv6rYtGPz86
This commit is contained in:
1 parent
3e3388c7fd
commit
358b859c59
2 files changed
+5
No files matched your search
@@ -35,6 +35,8 @@ services:
|
||||
- CMD-SHELL
|
||||
- pg_isready -U momentum -d momentum
|
||||
timeout: 5s
|
||||
# crash recovery after an unclean shutdown can outlast 5 x 10s (see truenas-compose.yml)
|
||||
start_period: 300s
|
||||
ports:
|
||||
- 5434:5432
|
||||
restart: unless-stopped
|
||||
|
||||
@@ -150,6 +150,9 @@ services:
|
||||
interval: 10s
|
||||
timeout: 5s
|
||||
retries: 5
|
||||
# crash recovery (WAL replay) after an unclean shutdown can outlast 5 x 10s; without a grace period
|
||||
# compose marks postgres unhealthy and refuses to start every dependent service (2026-09-30)
|
||||
start_period: 300s
|
||||
restart: unless-stopped
|
||||
|
||||
loop:
|
||||
|
||||
Reference in new issue
Block a user