a year ago
I had an issue with Postgres and my project is down. I can't access N8N. I'm in the middle of launching a digital product.
This is the log:
PostgreSQL Database directory appears to contain a database; Skipping initialization
2024-10-12 22:34:48.770 UTC [8] 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
2024-10-12 22:34:48.847 UTC [8] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-10-12 22:34:48.847 UTC [8] LOG: listening on IPv6 address "::", port 5432
2024-10-12 22:34:49.017 UTC [8] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-10-12 22:34:49.061 UTC [31] LOG: database system was interrupted; last known up at 2024-10-12 21:54:34 UTC
2024-10-12 22:34:49.096 UTC [31] LOG: database system was not properly shut down; automatic recovery in progress
2024-10-12 22:34:49.100 UTC [31] LOG: redo starts at 0/732C9DD0
2024-10-12 22:34:49.100 UTC [31] LOG: invalid record length at 0/732C9EB8: expected at least 24, got 0
2024-10-12 22:34:49.100 UTC [31] LOG: redo done at 0/732C9E80 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-10-12 22:34:49.121 UTC [29] LOG: checkpoint starting: end-of-recovery immediate wait
2024-10-12 22:34:49.142 UTC [29] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.015 s, sync=0.003 s, total=0.024 s; sync files=3, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB; lsn=0/732C9EB8, redo lsn=0/732C9EB8
2024-10-12 22:34:49.149 UTC [8] LOG: database system is ready to accept connections
I need help, please.
1 Replies
a year ago
I'm not seeing any issues with any of these services in the linked project.
> I'm in the middle of launching a digital product.
I don't mean to capitalize on your situation, but if you find yourself needing higher priority going forward; perhaps you would be interested in upgrading to the Pro plan?