12 days ago
My service has been down for over 40 minutes.
The container is wedged in "stopping" state and never finishes:
$ railway ssh
Your service's container is not running (status: stopping).
Deploy or restart your service, then try again.Symptoms:
-
Public URL returns 502 continuously.
-
Dashboard shows the deployment as ACTIVE / "Deployment successful" and the
service as Online, but nothing is actually serving.
-
"Restart" on the active deployment does nothing (no new container logs).
-
New deployments build fine (~14s, image pushed) but then hang forever at
"Deploy > Creating containers...". I aborted them; only the ACTIVE one is left.
-
Runtime logs still show the old container's output, never a new start.
Setup: US West, 1 replica, persistent volume "antas-volume" mounted at /data.
I suspect the wedged container still holds the replica slot and the volume,
so no new container can be scheduled.
Project: c52717f3-e49d-42c7-b808-55ed305e4e89
Service: ab380a97-57e2-46a1-9f76-94b36af0da4a (antas)
Environment: fe698473-97cd-4bfd-9c7d-472e58eac8b5
Could you force-kill the stuck container so a new one can be created? Thanks.
1 Replies
Status changed to Awaiting Railway Response Railway • 12 days ago
12 days ago
The container stuck in stopping is on our side, not yours. It never finished
tearing down, so it is still holding the mount and new containers cannot be
scheduled, which is what you are seeing as the 502 and the hang at creating
containers. Further redeploys will not clear it. Your volume is healthy and
your data is intact. We are clearing the stuck container from our side and
will confirm here once your service can deploy again.
Status changed to Awaiting User Response Railway • 12 days ago