Container stops
lcnewhook
PROOP

4 months ago

Hi. My ta-background stops immediately on restart. The deployment looks fine and deployes until healthcheck and the it gets a ═══════════════════════════════════════════════════════════

2025-11-19T06:03:34.058747713Z [inf]  ::ffff:100.64.0.2 - - [19/Nov/2025:06:03:33 +0000] "GET /health HTTP/1.1" 200 128 "-" "RailwayHealthCheck/1.0"

2025-11-19T06:03:36.000000000Z [inf]  Stopping Container

2025-11-19T06:03:45.048409364Z [inf]  stop_sign emoji SIGTERM received, shutting down gracefully...  I've tried re-deploying/restarting. Any ideas what is going on? thanks!

$10 Bounty

6 Replies

Railway
BOT

4 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


4 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody 4 months ago


lcnewhook
PROOP

4 months ago

I re-created the container and after a while I still had this issue again. Everything seems correct, but Railway keeps stopping the container.


angegabriel
FREE

4 months ago

what is your start command ?


lcnewhook
PROOP

4 months ago

Current: BLANK (using Dockerfile CMD)

Dockerfile: backend/Dockerfile

Actual command: dumb-init -- node index.js

I redeployed the container again, and it has already sent one stop_sign emoji SIGTERM received, shutting down gracefully... on a healthy container


angegabriel
FREE

4 months ago

Thanks. I hope index.jshas an HTTP server that stays listening?


angegabriel

Thanks. I hope index.jshas an HTTP server that stays listening?

lcnewhook
PROOP

4 months ago

Yes, index.js absolutely has a persistent HTTP server that stays listening. Current deployment is the longest survival yet (92+ min). We're monitoring to see if it remains stable or if Railway sends another premature SIGTERM. The earlier crashes (after 5 sec, 29 sec, 9 min) were caused by Railway sending SIGTERM prematurely despite the server being healthy and passing all health checks.


Loading...