25 days ago
Hi Railway team,
Production is down.
Project ID: b5c96610-f9ef-4944-b302-0bcfc0b04c83
Environment ID: 11aab17f-d32f-4672-85ca-9fc739fd55e9 production
API service ID: 6b90e53f-6e21-47f5-93da-5744a90521e4
Postgres service ID: 5dc68903-4eec-44d7-a9d7-cdaef1385ae6
Postgres deployment ID: ae0dc7d0-5ac1-42db-bd5a-01e8010f8d7c
Public API: https://mali-musavir-app-production.up.railway.app
API returns 502. API logs show Prisma P1001: cannot reach postgres.railway.internal:5432.
Postgres was crashed. After dashboard restart the Postgres deploy logs repeatedly show:
ERROR (catatonit:2): failed to exec pid1: No such file or directory
This looks like a Railway Postgres image/runtime/volume/internal networking issue after the platform incident. Production portal cannot log in because API cannot reach Postgres.
Please restore the Postgres service without resetting or deleting the volume.
1 Replies
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
I have redeployed your database, and it is back online. We sincerely apologize for the service disruption.
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