24 days ago
{"message":"ERROR (catatonit:2): failed to exec pid1: No such file or directory","severity":"error","attributes":{"level":"error"},"timestamp":"2026-05-20T09:03:42.005700933Z"}
2 Replies
24 days ago
have same Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:216:20) {errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
24 days ago
Your database service started crash-looping at 04:40 UTC on May 20 during a platform-wide service disruption that affected image registries and compute infrastructure. The "failed to exec pid1" error indicates the container image could not be loaded, which is consistent with that outage. The incident has since been resolved, so please try redeploying the service from the dashboard to restore it.
Status changed to Awaiting User Response Railway • 24 days ago
Status changed to Solved Railway • 24 days ago