PostgreSQL crashed: No space left on device, n8n workflows inaccessible
Anonymous
PROOP

24 days ago

"- My n8n service won't start up, returning a 503 error: 'Database is not ready!'

  • The PostgreSQL database has crashed and cannot recover

  • Error message in logs: 'could not write to file pg_wal/xlogtemp.25: No space left on device'

  • Additional errors: 'database system was interrupted while in recovery', 'This probably means that some data is corrupted'

  • Important workflows are stored in the n8n database that I need to recover

  • I've restarted both services multiple times, but the error persists

  • The PostgreSQL service keeps crashing (CRASHED status)"

$10 Bounty

2 Replies

Click on the volume mounted to your Postgres instance, go to settings, and increase the volume capacity.

Make sure to redeploy your Postgres service after.


karo123123123
HOBBY

23 days ago

1> Free up space, if you use docker prune unused images/volumes.
2> Start PostgreSQL alone Start only the DB service, not n8n, Check logs to confirm it can finish recovery.


Loading...