a month ago
Production managed-MySQL service (project optimistic-spontaneity, service MySQL, mysql-production-5131) crashed May 23. Root cause: an accidental railway up from the CLI overwrote the MySQL service's container image — logs show /bin/bash: docker-entrypoint.sh: command not found. The mysql-volume is intact and mounts cleanly on every boot (logs confirm). There are NO backups. I need to recover the data from the existing volume without modifying or reinitializing it. Please advise the safe procedure to start MySQL read-only against the existing volume and produce a mysqldump, or perform an internal recovery. Do not recreate or wipe the volume.
2 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
Have you tried creating a new MySQL service and attaching the existing volume to it?
Status changed to Solved chimimimusic • about 1 month ago
darseen
Have you tried creating a new MySQL service and attaching the existing volume to it?
a month ago
I had my CTO fix it. THanks.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago