MySQL service stuck in "unexpected state" after May 20 incident
fredrik-arvidsson
HOBBYOP

23 days ago

Hi,

My MySQL service is showing "Online" in the dashboard but the Database tab reports "Your application is not running or in a unexpected state" and "Database Connection: We are unable to connect to the database via SSH - Shell ready timeout, connection may be stale."

My application (Pastoralen) cannot connect to MySQL — repeated SocketTimeoutException: Connect timed out errors when Hikari/Flyway tries to establish a connection.

This started during the May 20 incident (KVZ1Z8GY) and has not recovered. I have restarted both the MySQL service and the application service multiple times without success.

Project: adorable-intuition

Environment: production

Region: EU West

MySQL deployment ID: e3ed3471

Plan: Hobby

Please advise — should I recreate the MySQL service, or is there an infrastructure issue on your end that needs intervention?

Thanks,

Fredrik

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 23 days ago


23 days ago

Your MySQL service's networking got into a stale state during the May 20 incidents. The database process is running, but the internal network route to it is broken, which is why your app sees connection timeouts while the dashboard shows it as online.

I've initiated a redeploy on our side that will resolve this. After the MySQL service is back and healthy, redeploy your pastoralen service as well. Your data volume is unaffected by either of these operations.


Status changed to Awaiting User Response Railway 23 days ago


Railway
BOT

16 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 16 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...