Worker service stops even with tail -f /dev/null
jaccoslok
HOBBYOP

21 days ago

Hi Railway Support,

Our worker service keeps stopping a few seconds after start. To isolate, I changed the start command to tail -f /dev/null and it still stops. That suggests the platform is sending SIGTERM, not the app.

Details:

  • Project: 871c4780-6e4f-4ce3-95d0-03d9751f5e03

  • Environment: 79dd6e01-b96b-44ae-98e1-0b9fdff51090

  • Service: 36e7d97c-e32a-4d2e-8b1a-0f54196a8f68

  • Deployment: e153347c-0b91-4567-b014-91da74ed47ee

  • Replica: cbcd956f-c377-4010-8a13-08ff609054ae

  • Timestamp of stop: 2026-02-22T13:18:08.075563166Z

Config:

  • Restart Policy: Always

  • Serverless: Off

  • Replicas: 1

  • Public networking: Off

  • Healthcheck: none

Could you check why the worker container is being stopped?

Thanks!

Solved$10 Bounty

Pinned Solution

jaccoslok
HOBBYOP

18 days ago

My worker was depending on a REDIS configuration, I forgot to add the REDIS_URL variable to the main web project. This caused stopping of the worker.

3 Replies

xmrafonso
FREETop 5% Contributor

21 days ago

Hey, have you checked logs? Any chances it's an Out of memory kill? It can also be another deployment (automatically) being triggered which kills the current one. Also, do you have a volume attached to the service/container?

jaccoslok
HOBBYOP

20 days ago

yes I have, I also checked the automatic deployment, there is no volume attached. The worker is intended for the REDIS database to do background tasks

jaccoslok
HOBBYOP

18 days ago

My worker was depending on a REDIS configuration, I forgot to add the REDIS_URL variable to the main web project. This caused stopping of the worker.

Status changed to Solved brody • 18 days ago

Loading...