a year ago
Hello, the linked volume is in an error state following Railway-initiated redeployment of the database service. Triggering another service deploy manually doesn't help, I believe a Railway team member will be needed here.
39 Replies
a year ago
Hello same problem for me 😕
a year ago
same here..
a year ago
Same for me, redeploying has worked but not great to have it go down unexpectedly.
a year ago
Same for me. Volume was already migrated to new region (if that's the reason of this automatic trigger) but results in "Volume migration failed". I did a "retry deployment" and it went through succesfully.
Now I have a second volume trying to migrate with "Waiting to migrate to new region.", which is already in the Metal/europe new region, it's been more than 60minutes, for ~150MB, and still "waiting to migrate"
a year ago
I’ve also had two Postgres deployments fail.
Same for me, it also happened on a Qdrant instance (as for a postgres instance, and 2 different environment with a Postgres on each of them)
a year ago
Same for (some of) our deployments.
a year ago
I had the same issue, but clicking redeploy manually seems to resolve it.
same here.. is there some info about this somewhere? was this a scheduled thing that I wasn't aware of?
a year ago
!t
a year ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response uxuz • 11 months ago
also.. it's pretty weird to have the message
Volume migration failed.
There was an error migrating your volume to the new region.
when i wasn't aware that my volumes were being moved to a new region.. which region is it going to?
That's just a generic error message. They are likely using the same mechanisms for this as region to region moves.
Same for me. I got random database deployment which was failed and no logs. But the app works as expected.
Same issue. My case: In two of my projects, postgres and redis are affected. App works, but I can't reach the tables in Postgres/Data on the dashboard.
a year ago
I have the same issue with the volume migration failing.
My django app appears to be working. I am a little inexperienced with deployment, so just wondering if there is anything I need to do?
a year ago
Hello,
okarmazin, I have raised your migration failure to the team.
For everyone else, please provide direct links to the service that has a failed migration.
@Brody to each service? in all environments? basically for me, it's every service in every environment that has an attached volume
actually, one of them didn't fail.. so it's 5 services in total, should I link them all?
a year ago
yes please
a year ago
Here is my service that shows the migration failure:
a year ago
a year ago
a year ago
a year ago
This also happened to me - both of my services have now been redeployed in the last two days (one of them failed the first time) and are working fine, but now the observability graph shows double the data usage for each of the two volumes, which has triggered my monitors. Is it possible that the volumes are now being double-tracked?
a year ago
Hello, my services failed again this morning :
a year ago
Hey there everyone,
So update, there are a variety of reasons why this would report the way it does and it's hard to exfil that information publicly.
However, what I can say is that we are working on a fix where if a Railway initiated migration fails (move your stuff to Metal!) it will not show as a red failure on your project. If you need a 1 to 1 manual migration from the Railway team, I would make a private thread with the team and we can work with you there.
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
On my side, I already migrated everything to Metal 2 or 3 months ago.
However in the past few days, I got 4 or 5 automatic deployments from railway telling me my services were being migrated to metal. Either volumes (where migration failed but was already on metal) or services (reporting successful metal deployment but was already in metal prior).
yes, moved to metal months ago, but my postgres volume still has a volume migration failed sticker on it.. is it safe to redeploy the service and will that resolve the volume migration failed error?
a year ago
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Awaiting User Response chandrika • 11 months ago
adelelsawaf
<https://railway.com/project/69b7bbfd-c33f-4ea5-99b8-412c134a04f7/service/26fa8933-edde-47ee-8048-9a4951a83a9e/settings?environmentId=fb618fa5-dc92-47ac-b52b-e585aaee0273> same problem for this service
a year ago
Hi there, I've responded on your private thread with us — you should be all set now 🙌
10 months ago
!s
Status changed to Solved brody • 11 months ago