Offline re: Temporary Performance Degradation Notice
geo
PROOP

a month ago

I've received a Temporary Performance Degradation notice for a stateful deployment (MySQL) 8 minutes ago. It said to last for 30 minutes and result in degraded performance. It is completely offline. Is this normal?

19 Replies

geo
PROOP

a month ago

Offline re: Temporary Performance Degradation Notice


geo
PROOP

a month ago

Railway's own console: Your service's container is not running (status: exited). Deploy or restart your service, then try again.


geo
PROOP

a month ago

It seems to have refused all connections for 30minutes now, dashboard claims it to be online but nothing can connect to it (incluidng the railway UI).


geo
PROOP

a month ago

@Chandrika any chance of escalation?


Please do not ping team members.


Are there any error logs?


geo
PROOP

a month ago

2026-06-10T15:19:34.831785Z 0 [System] [MY-015015] [Server] MySQL Server - start.

2026-06-10T15:19:34.948592Z 0 [Warning] [MY-015655] [Server] Server ignores the discovered container restrictions as --container_aware is OFF

2026-06-10T15:19:34.948618Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.7.0) starting as process 1

2026-06-10T15:19:34.948626Z 0 [System] [MY-015603] [Server] MySQL Server has access to 48 logical CPUs.

2026-06-10T15:19:34.948800Z 0 [System] [MY-015603] [Server] MySQL Server has access to 412550615040 bytes of physical memory.

2026-06-10T15:19:34.954949Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.

2026-06-10T15:19:35.150472Z 1 [Warning] [MY-012582] [InnoDB] io_setup() failed with EAGAIN. Will make 5 attempts before giving up.

2026-06-10T15:19:35.150529Z 1 [Warning] [MY-012583] [InnoDB] io_setup() attempt 1.

2026-06-10T15:19:35.650787Z 1 [Warning] [MY-012583] [InnoDB] io_setup() attempt 2.

2026-06-10T15:19:36.151062Z 1 [Warning] [MY-012583] [InnoDB] io_setup() attempt 3.

2026-06-10T15:19:36.651297Z 1 [Warning] [MY-012583] [InnoDB] io_setup() attempt 4.

2026-06-10T15:19:37.151565Z 1 [Warning] [MY-012583] [InnoDB] io_setup() attempt 5.

2026-06-10T15:19:37.651857Z 1 [ERROR] [MY-012584] [InnoDB] io_setup() failed with EAGAIN after 5 attempts.


geo
PROOP

a month ago

even for infra issues spanning 40mins ?


geo
PROOP

a month ago

image.png

Attachments


gkogkos-th
PRO

a month ago

Same issue with PostgreSQL. Deployment shows Online but dashboard can't connect and all app connections time out.

▎ Logs show:

▎ ERROR (catatonit:2): failed to exec pid1: No such file or directory

▎ repeating in a loop after volume mount.


geo
PROOP

a month ago

I got back online by migrating to US East from EU West (but by god it's slow)


geo
PROOP

a month ago

connections timing out -> railway official degradation notice -> deployment started crashing

45mins total now

not a peep from railway


geo
PROOP

a month ago

time and time again issues with stateful deployments that are not publicly acknowledged


Try pressing Ctrl/Cmd + K and redeploy from source.


I assume redeployments didn’t get it back online?


geo
PROOP

a month ago

crashloop


geo
PROOP

a month ago

innodb failed to initialize


gkogkos-th
PRO

a month ago

Ok that seems to fixed the issue so far. Thank you!


geo
PROOP

a month ago

So unlikely related to the OP, which is unacknowledged issues with railway metal infra/stateful deployments in EUW


Welcome!

Sign in to your Railway account to join the conversation.

Loading...