4 months ago
Hi,
My container on Hobby plan is stopping shortly after startup (around 7 seconds).
I see "Stopping Container" followed by SIGTERM in logs.
There is no deploy triggered at that time and no OOM message.
Can you check what is causing the restart?
Project ID: backgammon
5 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Can you share the exact deploy and logs/timestamps of those events? I'm unable to see any SIGTERMs in the deployment you linked to this thread.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
:
- Happens multiple times (not a single event).
- Logs show: "Starting Container" → "Server running" → "Stopping Container" → "npm error signal SIGTERM" (no stack trace, no OOM).
- Server listens on
process.env.PORTand0.0.0.0. - Does it happen due to platform restarts/maintenance or healthcheck timeouts? Any way to see the exact restart reason
Status changed to Awaiting Railway Response Railway • 4 months ago
ray-chen
Can you share the exact deploy and logs/timestamps of those events? I'm unable to see any SIGTERMs in the deployment you linked to this thread.
4 months ago
attach screen shot
Attachments
4 months ago
The SIGTERM was likely from a redeploy if you're viewing them in the "Logs" tab - that comes all logs from your project/multiple services. Can you link to an exact deploy that was SIGTERM'd that did not result from a redeploy?
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 4 months ago