Postgre DB failure

sleepydreams-tb

HOBBYOP

a month 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"}

Solved

2 Replies

gadatos

PRO

a month 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'

}

Railway

BOT

a month 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 • about 1 month ago

Status changed to Solved Railway • about 1 month ago

Welcome!