9 months ago
Hi Railway Support,
I need urgent help recovering access to my Database (MongoDB) after a migration/recreation incident.
Background: My Database service was migrated/recreated by Railway, but I retained the original data volume. If it wasn't for this migration, I wouldn't be in this situation - everything was working perfectly before.
Problem: The new Database container has different initialization credentials than what's stored in the volume's authentication system. This is causing startup failures with "Error during global initialization" and I cannot access my data.
What I need: Access to my Database again. I have all my application data in the volume - I just need to get the Database service running.
Can Railway help me either:
Restore the original Database initialization credentials that were used with this volume?
Reset the volume's authentication system while preserving my application data?
Provide an alternative way to access my data from this volume?
This is blocking my entire application. I wouldn't have encountered this issue if the migration hadn't initially occurred.
Please help - thank you!
10 Replies
9 months ago
Hi - I'm seeing the mongodb service up, could you please link the specific deployment where you're seeing this error?
Status changed to Awaiting User Response Railway • 9 months ago
sarahkb125
Hi - I'm seeing the mongodb service up, could you please link the specific deployment where you're seeing this error?
9 months ago
Hi,
It's the volume called 'database' that's what I need to be up and running with a Mongo service.. The instance you see is me trying to frantically get my stuff up and running (to an extent) but it's that volume I need mounted and connected..
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
What happens when you click "mount" on the volume?
Status changed to Awaiting User Response Railway • 9 months ago
sarahkb125
What happens when you click "mount" on the volume?
9 months ago
If you look at my environment, you can see the data mounted to a mongodb instance, but the database connection does not establish.
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 9 months ago
9 months ago
Hi there - mongo is back up.
We removed the --noauth flag in the start command.
We're still investigating why this happened, but you should be unblocked!
Status changed to Solved sarahkb125 • 9 months ago
9 months ago
Question - did you happen to add the flag during the debugging process?
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
Hey, yes I did - I spent a while reading online about how to attempt to debug. I'll leave this as is for now, and attempt to reconnect my containers tomorrow if that's okay? Thank you again for the extremely swift response.
9 months ago
All good!
Status changed to Awaiting User Response Railway • 9 months ago
9 months ago
Let us know if you have any other issues - should be up and running.
Status changed to Solved sarahkb125 • 9 months ago
9 months ago
✅ The internal ticket Error during global initialization - volume mount has been marked as completed.