a month ago
Our celery workers randomly shut down out of nowhere. The error message implicates they are shutdown by railway.
our memory and CPU levels are under our limit for the whole time the workers are running
the error message says "Got shutdown from remote, Stopping Container" implicating the service was stopped by railway
no errors occured in the logs directly before the shutdown
our workers build without problems (example build script in attachments)
we deploy our workers through github with .sh build scripts
only 4 out of 6 deployed workers were shutdown by this error
logs from the workers can be seen in attachments
the workers run fine for a few days and then crash out of nowhere
13 Replies
a month 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!
a month ago
It would seem as if you are looking at your previous deployments. When a new deployment goes out, we shut down the older deployment.
Status changed to Awaiting User Response Railway • 27 days ago
a month ago
I moved my message to the thread
Status changed to Awaiting Railway Response Railway • 27 days ago
brody
It would seem as if you are looking at your previous deployments. When a new deployment goes out, we shut down the older deployment.
a month ago
Hi Brody, that actually isn't the case here. This specific deployment had been active and running for multiple hours before the shutdown occurred.
We did not push any new code or trigger a new deployment at that time. The logs just stopped with "Got shutdown from remote" spontaneously after hours of uptime, without a new deployment taking its place.
Status changed to Awaiting User Response Railway • 27 days ago
noahd
Do you have a link to that specific deploy? I don't see much on our end
a month ago
Status changed to Awaiting Railway Response Railway • 27 days ago
Status changed to Awaiting User Response Railway • 27 days ago
brody
That deployment was shut down because of a newer deployment.
a month ago
Yeah but at Feb 6, 2026, 1:59:13 PM GMT+1 you can see there was a log "Got shutdown from remote" and I created the newer deployment on Feb 6, 2026, 6:47:26 PM GMT+1 and that was almost 5 hours after the server got shutdown from remote
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Sure but Got shutdown from remote wasn't initiated by us, the Stopping Container was.
Status changed to Awaiting User Response Railway • 27 days ago
brody
Sure but Got shutdown from remote wasn't initiated by us, the Stopping Container was.
a month ago
Are you sure? Because this is not an error from Celery or Django either
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Hello, I'm not really familiar with celery. From a quick cursory search it looks like this was due to the worker receiving an external shutdown command.
Status changed to Awaiting User Response Railway • 27 days ago
brody
Sure but Got shutdown from remote wasn't initiated by us, the Stopping Container was.
a month ago
Could you clarify why you stopped the container? It's as if the celery service got a SIGTERM signal, we believe it came from railway, since we didn't do any changes. The new deployment was done manually, to fix the broken services. Therefore the message shutting down containers and "got shut down from remote" isn't caused by running a new deployment. It occured before the manual deployment fixing the problem.
Status changed to Awaiting Railway Response Railway • 26 days ago
a month ago
We did not send any shutdown signal when your application printed the Got shutdown from remote log.
I'm sorry but we will not be able to help out here further as we do not offer application level support, so I will go ahead and open this up to the community so they can possibly help you debug.
Status changed to Awaiting User Response Railway • 26 days ago