25 days ago
Hello, in my procjet "whats-shop" (the only one that i have) I am experiecing the error "failed to exec pid1: No such file or directory" in loop after restart at the postgree database. It happened during the 19/05 incident. My dashboard is on, but there is no data there.
Note: I am not a programmer, I used claude to vibe code the solution.
it's obvious that the error is related to the outage, but do I just wait some hours and try to rebuild or there is something else that I need to do?
3 Replies
25 days ago
Your Postgres service is in a crashed state and needs a redeploy to recover from the May 19 service disruption. You can trigger a redeploy from the three-dot menu on the latest deployment. However, builds on Hobby plans are temporarily paused right now while we clear a backlog, so the redeploy may be delayed until that resolves. Your data on the attached volume should still be intact once the service comes back up.
Status changed to Awaiting User Response Railway • 25 days ago
Railway
Your Postgres service is in a crashed state and needs a redeploy to recover from the [May 19 service disruption](https://status.railway.com/incident/I23M92U0). You can trigger a redeploy from the three-dot menu on the latest deployment. However, builds on Hobby plans are [temporarily paused](https://status.railway.com/incident/KVZ1Z8GY) right now while we clear a backlog, so the redeploy may be delayed until that resolves. Your data on the attached volume should still be intact once the service comes back up.
25 days ago
Just restarting the postgree is not enough, right? I need to redeploy it.
Status changed to Awaiting Railway Response Railway • 25 days ago
25 days ago
That's correct, you need to redeploy rather than just restart. A restart reuses the same deployment image, which in this case is broken. A redeploy triggers a fresh build. You can do this from the three-dot menu on the latest deployment in your Postgres service. Note that builds on Hobby plans are temporarily paused while we clear a backlog from the earlier incident, so there may be a delay before it processes - you can track that here. Your data on the volume should be intact once the service is back up.
Status changed to Awaiting User Response Railway • 25 days ago
Status changed to Solved pedroctrautwein • 25 days ago