4 months ago
It crashes just few mins after restarting. sometime even few seconds.
- tried to re deploy too. Now it just crash immediately and error is "No space left on device"
I do have empty space, usage/credits as I increased from 500mb to 5gb.
It looked like there were empty space even when it was 500mb
space 5gb and I am on the hobby plan.
logs are like below
What would be the problem?
Data was working fine in mongodb atlas
Attachments
5 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Thank you for replying.
I need to dump my data first as there are some updated data. I need those of them.
I tried option2 as there is backup to restore. but this was not working.
Yeah once I dump these data, I will move back to MongoDB Atlas
But now I am still stuck in this situation.
4 months ago
Could you tell me how to unmount the mongodb volum from existing mongoDB service?
I can't find way to unmount on dashboard.
Option2 wasn't successful. It seems like starting little bit longer after dpeloy with the given startup command. However, I can''t connect to mongodb these time.
4 months ago
I am tryting to follow you.
I re-deploy the MongoDB service with your start command.
It seems like it is stuck at apt-get install
below is logs
Previously, I also try to detach volume with railway cli.
Detacihng was successful. but Couldn't attach volume to linux service with CLI.
I could manage to attach volume to linux service on dashboard.
However, "railway run ls /" didn't show /data/db
Attachments
4 months ago
form reading package list, it never change something for half an hour is more than enough. isn't it?
I also tried just ls -la. but the log is just "Starting Container"
I assume something related to volume never work
4 months ago
It is fixed with raiway private asking
Status changed to Solved dogyunjeong • 4 months ago