a month ago
Re-deploying the Postgres instance does not seem to help, it still immediately crashes with the following error.
ERROR (catatonit:2): failed to exec pid1: No such file or directory
This is mildly concerning, given that the incident is marked as "resolved" and the incident team reportedly went to bed.
What can I do to get my database back? Or when can I expect the incident to be actually resolved?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
To anyone else having the same problem:
I was on :18 which apparently is a moving target and seems like the newest minor version 18.4 was broken. I pinned it to :18.3 in Settings and redeployed, which fixed my issue.
Be careful not to change major versions, in case of incompatible data storage though (unless you trust your backups).
Status changed to Solved tskj • about 1 month ago