a month ago
{ "message": "Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/dc861ff1-91e4-4c71-ab32-5797f35c8cf8/vol_km4hx1bkkxu8yq48", "attributes": { "level": "info" }, "tags": { "project": "7f7e6588-990a-4c5a-b59f-b4d00a6528eb", "environment": "845eb71f-1ea6-4a4e-a0bb-e6b46444ffb4", "service": "af81dbcf-547f-4190-86e4-698eeab0dae8", "deployment": "295b63fd-ed79-4963-9db3-10161ae0df21", "replica": "dc861ff1-91e4-4c71-ab32-5797f35c8cf8" }, "timestamp": "2026-02-11T14:50:12.000000000Z" }
My Meilisearch volume was automounted which downed my server for 2 hrs, and it didn't kill the Meilisearch or Backend container, backend services started responding 502 , which further downed the frontend, while containers kept running and no warning from Railway
I redeployed my backend which gave error on connecting to Meilisearch on healthchecks
once i redeployed the Meilisearch container , and than Backend container it started working
Why there is no notification of Meilisearch volume being mounted from Railway's side, is it a ususal practice , as it disrupted my running backend for 2 hrs?
1 Replies
a month ago
Hello,
We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.
You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026
Our deepest apologies for the inconvenience this has caused.
Status changed to Awaiting User Response Railway • 29 days ago
22 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 • 22 days ago