a month ago
My production db isn't reachable and the dashboard says there's been a hardware failure on the server hosting the container. How can I mitigate this? I can't spin up a new replica because it says it has a volume attached and a redeploy gets stuck in creating the container.
6 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I tried cmd k and redeploy from source image but still stuck. Guys at the railway team, do you know when your servers will be back online?
a month ago
Theres a hardware problem at the moment, and you're probably affected. You can follow the status by the banner above the dashboard. You should also have received an email if you were impacted
danny
Theres a hardware problem at the moment, and you're probably affected. You can follow the status by the banner above the dashboard. You should also have received an email if you were impacted
a month ago
yes I know thank you but I need to find a solution to redeploy the db. it's also the prod one by luck. the dev one works fine. ahhh
a month ago
Because the node is offline Railway can't pull any data from the volume, and thus can't deploy to another mode. You can try restoring a backup from the backup tab if possible. If you have any external backups you can temporarily Create a new service with this backup. If you don't have any of these then unfortunately you're gonna have to wait.
a month ago
ok it's online again. if you still have any tips on how to avoid these situations let me know
Status changed to Solved pietro-bonfada • about 1 month ago