Skip to content
service europe-west4, 1 replica, volume at /data, no healthcheck, 1 GB limit.
burnoutspecial
OP

19 days ago

After the migration from US West to EU West on Oct 31, our service was stopped by the platform with no successor deployment, and stayed down until a manual redeploy:

  1. Oct 31 12:41:40 UTC: the running container was stopped ("Stopping Container", no app error before it). Nothing started again until 13:32 UTC.
  2. Oct 31 13:47:23 UTC: deployment 7d67b82d (commit f9f3a9c) was stopped about 3 minutes after it started serving requests normally. No newer deployment was created and no OOM is visible. The service stayed down (502) until a manual redeploy (1c5699ae, same commit, same config) at Nov 2 09:42 UTC, which is still running fine.

Pattern: deployments triggered by a GitHub push or a variable change get stopped, while a manual Restart or Redeploy works.

Could you check what is stopping these containers on your side, and whether it is related to the region migration?

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 19 days ago


Railway
BOT

19 days ago

Your Nov 2 09:42 UTC redeploy (1c5699ae) completed normally and is the deployment currently running. The deployment records we can read don't go back far enough to establish what stopped the Oct 31 containers or whether the region migration was involved.

On the pattern you noticed: because this service has a volume, every new deployment stops the previous one before the new one starts, since two deployments can't mount the same volume at once. Push- and variable-triggered deploys therefore always include a short stop. That doesn't explain a stop with no replacement deployment, which is what you describe at 12:41 and 13:47 UTC.

To assess those two stops, please share:

  • the full deployment ID of the container stopped at 12:41 UTC, and the full ID of 7d67b82d
  • the status each deployment shows in the dashboard (for example Failed, Crashed or Removed)
  • any error or message in their deploy logs around those times, with secrets redacted
  • what triggered each one (push, variable change or manual action)
  • the IDs and UTC times of any other push- or variable-triggered deployments that stopped the same way

Status changed to Awaiting User Response Railway • 19 days ago


Railway
BOT

12 days 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 • 12 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...