25 days ago
Hi, has anyone seen this before?
Our Railway Postgres service starts normally, finishes recovery, becomes ready to accept connections, and then about 1 minute later the logs show "sending signal SIGTERM to container" and it stops.
Important detail:
- I redeployed only the Postgres service
- all other app services were offline during the test
- CPU and memory are low/stable
- a volume is mounted at /var/lib/postgresql/data
So this does not seem to be caused by app traffic.
I only have worker access to this shared project, so I could not select the service in the support form.
Project details:
- Project ID: 3168ca49-649f-48d9-bf9a-26d0ca8a6fcd
- Service ID: d8b30a04-b6e4-4218-8fe5-1af4cf17e98a
- Deployment ID: 817785e5-d412-48df-b060-3df526697ae2
Has anyone seen Railway terminate a Postgres container like this shortly after startup?
2 Replies
25 days ago
The project is on the Free plan, which includes only $1 of monthly credit and limits volume storage to 0.5 GB. The SIGTERM roughly one minute after startup is consistent with the workspace hitting its usage limit for the billing cycle, which causes all workloads to be shut down automatically. The workspace admin should check the Workspace Usage page to see if the hard limit or credit has been exhausted, and also verify that the Postgres volume has not exceeded the 0.5 GB Free plan volume limit.
Status changed to Awaiting User Response Railway • 25 days ago
25 days ago
The volume usage on postgres is still on 113Mb
Attachments
Status changed to Awaiting Railway Response Railway • 25 days ago
Status changed to Open Railway • 25 days ago
Status changed to Solved henriquefernandes-hbf • 25 days ago