Production MySQL service is unavailable and Railway cannot start a replacement instance. Project ID: 23cbd24e-9e48-470f-9914-465db836fe3c Environment ID: 9f96cc27-b5f8-4eb1-b18a-28c9ec8a3833 Service ID: 4f0da0b3-9620-47c9-86f3-3c80895a4a14 Region: US West / us-west2 Volume: playground-volume Volume ID: e06a3367-6a5b-4d72-b137-3edc235d15b1 Aborted redeployment ID: 7e460f3b-21d1-42a6-bf85-198a41075214 Observed behavior: - The service is shown as Online/Active, but the Database tab remains indefinitely on “Attempting to connect to the database”. - The Console reports “No running instances” / disconnected. - Application logs repeatedly report PROTOCOL_CONNECTION_LOST and “The server closed the connection”. - CPU, memory, and network metrics are all zero. - A normal Restart request failed in the UI with “Problem processing request”. - Patch Now appeared to complete, but no new deployment or backup/snapshot was created and the patch banner remained. - A Redeploy remained at “Creating containers...” for over 23 minutes, with no deploy logs and post-deploy never starting. It was then manually aborted. - Required database variables are present and unchanged. The persistent volume remains attached. - Railway’s public status page reports operational, so this appears to be an isolated provisioning or volume-attachment issue. Please inspect the internal container/deployment and volume attachment state and recover the MySQL service without deleting, detaching, or recreating the persistent volume. Preserving the existing database data is critical.

MySQL service unavailable; restart fails and redeploy stuck creating containers

kanarikus

HOBBYOP

2 days ago

Production MySQL service is unavailable and Railway cannot start a replacement instance.

Project ID: 23cbd24e-9e48-470f-9914-465db836fe3c

Environment ID: 9f96cc27-b5f8-4eb1-b18a-28c9ec8a3833

Service ID: 4f0da0b3-9620-47c9-86f3-3c80895a4a14

Region: US West / us-west2

Volume: playground-volume

Volume ID: e06a3367-6a5b-4d72-b137-3edc235d15b1

Aborted redeployment ID: 7e460f3b-21d1-42a6-bf85-198a41075214

Observed behavior:

The service is shown as Online/Active, but the Database tab remains indefinitely on “Attempting to connect to the database”.
The Console reports “No running instances” / disconnected.
Application logs repeatedly report PROTOCOL_CONNECTION_LOST and “The server closed the connection”.
CPU, memory, and network metrics are all zero.
A normal Restart request failed in the UI with “Problem processing request”.
Patch Now appeared to complete, but no new deployment or backup/snapshot was created and the patch banner remained.
A Redeploy remained at “Creating containers...” for over 23 minutes, with no deploy logs and post-deploy never starting. It was then manually aborted.
Required database variables are present and unchanged. The persistent volume remains attached.
Railway’s public status page reports operational, so this appears to be an isolated provisioning or volume-attachment issue.

Please inspect the internal container/deployment and volume attachment state and recover the MySQL service without deleting, detaching, or recreating the persistent volume. Preserving the existing database data is critical.

Awaiting User Response

2 Replies

Status changed to Awaiting Railway Response Railway • 2 days ago

keshavsoni17

PRO

2 days ago

Getting same issue, but with Redis deployment. It's crazy how Railway hasn't updated it's status page despite so many issues.

nico

EMPLOYEE

2 days ago

Your MySQL volume is on a host in US West that became unresponsive at about 14:15 UTC and was restarted at about 16:30 UTC. That's why Restart returned an error and the redeploy sat at "Creating containers": a database has to start on the same host as its volume, and that host was down.

Nothing was deleted, detached, or recreated. playground-volume is still attached to the MySQL service on that same host, which is back now. Redeploy the MySQL service once, and it will start on that existing volume.

You were right that this wasn't on your side. It's covered by this incident: https://status.railway.com/incident/72DDHCC1

Status changed to Awaiting User Response Railway • 2 days ago

Welcome!