8 months ago
2025-03-26 18:32:07.462 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-03-26 18:32:07.462 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-03-26 18:32:07.462 UTC [2] LOG: listening on IPv6 address "::", port 5432
2025-03-26 18:32:07.466 UTC [2] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-26 18:32:07.471 UTC [25] LOG: database system was interrupted while in recovery at 2025-03-26 18:32:04 UTC
2025-03-26 18:32:07.471 UTC [25] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2025-03-26 18:32:07.505 UTC [25] LOG: database system was not properly shut down; automatic recovery in progress
2025-03-26 18:32:07.508 UTC [25] LOG: redo starts at 0/3CB7F790
2025-03-26 18:32:07.643 UTC [25] LOG: redo done at 0/3FFFF4B8 system usage: CPU: user: 0.04 s, system: 0.09 s, elapsed: 0.13 s
2025-03-26 18:32:07.672 UTC [25] FATAL: could not write to file "pg_wal/xlogtemp.25": No space left on device
2025-03-26 18:32:07.676 UTC [2] LOG: startup process (PID 25) exited with exit code 1
2025-03-26 18:32:07.677 UTC [2] LOG: terminating any other active server processes
2025-03-26 18:32:07.677 UTC [2] LOG: shutting down due to startup process failure
2025-03-26 18:32:07.685 UTC [2] LOG: database system is shut down
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/52e20106-3ebc-4532-b022-9018e14d4c83/vol_2230avqtzdxf9emt
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-03-26 18:32:10.689 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-03-26 18:32:10.690 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-03-26 18:32:10.690 UTC [2] LOG: listening on IPv6 address "::", port 5432
2025-03-26 18:32:10.695 UTC [2] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-26 18:32:10.701 UTC [25] LOG: database system was interrupted while in recovery at 2025-03-26 18:32:07 UTC
2025-03-26 18:32:10.701 UTC [25] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2025-03-26 18:32:10.736 UTC [26] FATAL: the database system is starting up
2025-03-26 18:32:10.740 UTC [25] LOG: database system was not properly shut down; automatic recovery in progress
2025-03-26 18:32:10.742 UTC [25] LOG: redo starts at 0/3CB7F790
2025-03-26 18:32:10.888 UTC [25] LOG: redo done at 0/3FFFF4B8 system usage: CPU: user: 0.03 s, system: 0.10 s, elapsed: 0.14 s
2025-03-26 18:32:10.900 UTC [25] FATAL: could not write to file "pg_wal/xlogtemp.25": No space left on device
2025-03-26 18:32:10.906 UTC [2] LOG: startup process (PID 25) exited with exit code 1
2025-03-26 18:32:10.906 UTC [2] LOG: terminating any other active server processes
2025-03-26 18:32:10.906 UTC [2] LOG: shutting down due to startup process failure
2025-03-26 18:32:10.913 UTC [2] LOG: database system is shut down
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/52e20106-3ebc-4532-b022-9018e14d4c83/vol_2230avqtzdxf9emt
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-03-26 18:32:13.653 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-03-26 18:32:13.653 UTC [2] LOG: listening on IPv4 address "0.0.0.0", port 5432
6 Replies
8 months ago
Hey, is this a newly deployed and therefore empty Postgres database? If so, try deploying a new Postgres database from your project's dashboard.
8 months ago
I was trying to delete some old executions to try to free up Postgres database, but it caused and error, so I tried to rollback the database.
Now the database and primary won't work for n8n deployment
yueli09
I was trying to delete some old executions to try to free up Postgres database, but it caused and error, so I tried to rollback the database. Now the database and primary won't work for n8n deployment
8 months ago
Since your database is in an unrecoverable state anyway, do you mind wiping the volume so that Postgres can initialize itself again? You may also want to redeploy the other services that depend on it once you have wiped the volume. In this case, all the data that was previously on the volume will be deleted, so do this at your own risk.
8 months ago
There's no way to recover my previous projects?
yueli09
There's no way to recover my previous projects?
8 months ago
No there is no way, unless you have made a backup.
8 months ago
Hey Yueli, going to close this out but please feel free to reopen, or open another thread if you have any more questions around this or anything else!
Status changed to Awaiting User Response Railway • 9 months ago
Status changed to Solved chandrika • 9 months ago