#Postgres container crash-looping — failed to exec pid1

3 messages · Page 1 of 1 (latest)

foggy elk
#

Hi, my Railway Postgres service has been crash-looping since around 04:53 UTC today (20 May). The logs show repeated:

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

The container mounts the volume successfully but then immediately fails to start. This is affecting a production application. Project ID: 60ac0747-86a2-4bfe-9839-893f04ab8041, Service ID: 7fc6d3f8-b93c-4b9f-93e1-0af5a35ea6c8.

I've also noticed what appears to be external port scanning of the Postgres port over the past week (repeated failed SSL connection attempts from external IPs). Not sure if related.

Is there a known issue with Postgres on Railway today? Any ETA on a fix?

shy coralBOT
#

Is this about a specific service? Linking one helps us understand your setup.

hasty nova
#

Hey, you can fix this by redeploying the postgres container. It has to be a redeploy, not a restart.

This might take a while as I know there's an open incident to deal with slow builds. Really deeply sorry you're going through this.