a month ago
Hi Team,
I was using N8N and the Postgresql crashed, there is no backup option provided and the Resze is also not having any impact
Please help.
5 Replies
a month ago
Your Postgres service is crash-looping because the volume has run out of disk space, preventing WAL recovery from completing. You need to perform a live resize on the volume - since it's at 100% capacity, the system will automatically do an offline resize with data integrity checks and restart the service, which should allow Postgres to recover. For future protection, we recommend setting up automated backups on the volume from the service's Backups tab.
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Thanks for the response,
The issue is still not resolved,
Please could we connect regarding this.
Would be much appreciated.
Regards,
Ansh
a month ago
Your Postgres service is still showing as crashed. After performing the volume resize, you need to redeploy the service for the changes to take effect. You can do this by clicking the three-dot menu on the active deployment and selecting "Redeploy". If the service continues to crash after redeploying, let us know and we can investigate further on our end.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
I have resized it to 5 gbs and redeployed it as well.
The service is still crashing, could you please investigate.
Would really appreciate.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey Ansh, the volume resize you performed didn't fully apply on our end. We've corrected this and redeployed your Postgres service. You should now have the full 5 GB of disk space available.
We also recommend enabling automated backups from your service's Backups tab to protect against data loss in the future.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 30 days ago