8 months ago
I was hosting n8n and it crashed. In the logs, it looked like an invalid credential was the 1st issue. It is also an issue with Postgres, I will put some of the logs I see below.
I really need to get the n8n workflows I built back. Please help with this.
LOGS:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-07-17 02:43:49.618 UTC [2] LOG: starting PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-07-17 02:43:49.618 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-07-17 02:43:49.618 UTC [2] LOG: listening on IPv6 address "::", port 5432
2025-07-17 02:43:49.626 UTC [2] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-07-17 02:43:49.639 UTC [25] LOG: database system was interrupted while in recovery at 2025-07-17 02:43:41 UTC
2025-07-17 02:43:49.639 UTC [25] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2025-07-17 02:43:49.676 UTC [26] FATAL: the database system is starting up
2025-07-17 02:43:49.704 UTC [25] LOG: database system was not properly shut down; automatic recovery in progress
2025-07-17 02:43:49.710 UTC [25] LOG: redo starts at 0/30C20840
the database system is starting up
the database system is not yet accepting connections
2025-07-17 02:43:49.979 UTC [27] FATAL: the database system is not yet accepting connections
2025-07-17 02:43:49.979 UTC [27] DETAIL: Consistent recovery state has not been yet reached.
2025-07-17 02:43:50.217 UTC [25] LOG: redo done at 0/3BFFFDF0 system usage: CPU: user: 0.14 s, system: 0.35 s, elapsed: 0.50 s
2025-07-17 02:43:50.235 UTC [25] FATAL: could not write to file "pg_wal/xlogtemp.25": No space left on device
2025-07-17 02:43:50.241 UTC [2] LOG: startup process (PID 25) exited with exit code 1
2025-07-17 02:43:50.241 UTC [2] LOG: terminating any other active server processes
2025-07-17 02:43:50.241 UTC [2] LOG: shutting down due to startup process failure
2025-07-17 02:43:50.255 UTC [2] LOG: database system is shut down
Pruning old insights data
Pinned Solution
5 Replies
8 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 PostgreSQL crashed: No space left on device, n8n workflows inaccessible"
🧵 PG volume not showing as full, but PG having no space on disc
🧵 🧷 Title: Help! PostgreSQL Crashing – “No space left on device” (Hobby Plan)
If you find the answer from one of these, please let us know by solving the thread!
8 months ago
Hey. Your volume is full. You'll need to resize it under Volume -> Settings -> Size -> Grow.
ray-chen
Hey. Your volume is full. You'll need to resize it under Volume -> Settings -> Size -> Grow.
8 months ago
This is a dumb question but where can I find volume? Thank you :)
phoenixauro
You can see it just below your service
8 months ago
It was right in front of me lol. That worked and I'm back in business! Thanks so much!
Status changed to Solved chandrika • 8 months ago