9841789e-8487-4afa-ab8b-2e53a0fbb8f2

mind sending a screenshots of the top part of your service settings?

thank you, and when was the last succesful deploy of your MySQL database?

the deployments still work fine, but the connection is no longer possible. I tried to migrate today, so deployments older than 1 day were working

so does it work when you redeploy it on a GCP region?

I will try

To me it looks like the redeploy is making the mysql server want to update, but it fails because it's trying to delete something it's not allowed to delete

The migration to GCP has just finished, but the problem persists

The logs seem to be the same

yea, that's what I thought

so it's not metal, it's just failing to update your mysql server

so the latest working deployment is a day old?

if I can have the timeframe then I can try tracking down the specific version

Ok okay, so it's certainly related to the fact that the release points to mysql:8 Docker image and therefore a minor release has been incremented due to a new deployment?

well I'm not sure, that's just my theory

From several months ago… 😅

how many months ago?

3 months

Dec 27, 2024 2:14 AM

mysql 8 was on mysql 8.4.3 three months ago
mysql 8.4.4 released 2 months ago

from the logs, it does seem like it's starting an 8.4.4 server

Do you have a backup of the database?

cause we probably shouldn't mess with the versions without having a backup

Do you know if the rollback button restarts a build? Or does it really use the previous build (and therefore the exact version that was there)

it redoes the build with the same configurations, but I'm not sure that'll help cause it'll still pull from mysql:8 which I think now routes to 8.4.4

nop

and you're not on pro plan so you can't do one from railway's side huh..

this is quite the pickle

and on this workspace I'm not a pro user, so I can't create a backup

there is one thing we could try, but it's kinda scuffed
you could go into your project settings, go to environments, enable PR environments with copy volume data enabled
that way it copies your database into a new service when you create a PR, then create a PR for your service
railway will then create a duplicate environment for you
then on your created PR environment you could try changing your database version to 8.4.3 and see if it works before doing it in the production environment

or if you don't care about the data in the database you could just try going mysql:8.4.3 directly and see what happens

I'm willing to take the risk: if there's a 30%+ chance that a version change will break the data, then I could code a service to retrieve the content of the voume before the version change

I don't think there's a major risk of data loss here, but if the data is important then i don't think any amount of risk is worth it

I'll test it with PR environments!

alright, def the safer approach

i'm gonna go eat the sushi I ordered and I'll be back in a bit, good luck! 🫡

Thank you for your help and "bon appétit"🇫🇷!

🤣 thank you

ah that is no bueno

seems it can't revert cause the upgrade already started

I'm out of ideas

yes, I'll try other things by downloading the data of the volume!
thanks for your help and the hints you gave me! 💯

no problem, good luck with this
sorry that I wasn't able to offer more help

It's already a lot!

$wa

$s

💀

!s