25 days ago
We had a managed Postgres service using ghcr.io/railwayapp-templates/postgres-ssl:18 fail with:
catatonit: failed to exec pid1
The service had startCommand set to:
wrapper.sh postgres --port=5432
After the platform recovered/restarted, Postgres is online again with the original volume, but GraphQL still reports the same custom startCommand. Please confirm whether this custom startCommand is expected for managed Postgres, and if not, clear it from the platform side.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
The failure occurred during the service disruption on May 20, which is why Postgres recovered on its own once the platform stabilized. The wrapper.sh postgres --port=5432 start command is the default entrypoint baked into the postgres-ssl image, so having it also set as a custom startCommand is redundant. You can clear it yourself in the service's Settings tab under "Start Command" - the image's built-in entrypoint will take over automatically.
Status changed to Awaiting User Response Railway • 25 days ago
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago