n8n Primary fails to deploy ("could not open file base") after running VACUUM FULL in Postgres
krmbckr
PROOP

8 months ago

I use n8n With Workers in Railway. My volume in Postgres was abnormally high so I deleted old execution data and logs to clear up space (I did upgrade to Pro and increase my volume, but it is still way too high at 7GB for only 4 simple active workflows running).

The space was not cleared up after deleting the excess data (using dbGate) so I ran a VACUUM command. That didn't reduce the volume noticeably, so I ran VACUUM FULL per guidance online. I redeployed Postgres, but now I cannot deploy n8n Primary as it keeps crashing. The Deploy Logs show

"There was an error initializing DB

could not open file "base/xxxxx/xxxxxx": No such file or directory

Last session crashed"

Please can you help me fix this? I tried following all instructions online to fix the abnormal Volume but now I am completely stuck and don't know how to recover whatever VACUUM FULL deleted but was actually needed.

Thank you so much for your help

$10 Bounty

3 Replies

Railway
BOT

8 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


krmbckr
PROOP

8 months ago

Could the Railway team please help restore the deleted/ corrupted files?


krmbckr
PROOP

7 months ago

Railway team -- please could you fix this on your end? I think it requires your help on the back-end


Loading...