PostgreSQL Issues on N8N implementation
tim-nocode
PROOP

a year ago

Hi everyone!

I’m encountering an issue with PostgreSQL on my N8N implementation. Whenever this error appears, the server becomes unreachable. I’m facing the same problem across two N8N implementations. Does anyone know how to fix this?

2024-08-26 11:05:32.930 UTC [30] LOG: checkpoint starting: time

Aug 26 13:10:02

2024-08-26 11:10:02.303 UTC [30] LOG: checkpoint complete: wrote 4156 buffers (25.4%); 0 WAL file(s) added, 0 removed, 2 recycled; write=269.070 s, sync=0.139 s, total=269.373 s; sync files=25, longest=0.027 s, average=0.006 s; distance=33654 kB, estimate=33654 kB; lsn=1B/F3249E98, redo lsn=1B/F31E3678

Aug 26 13:10:32

2024-08-26 11:10:32.330 UTC [30] LOG: checkpoint starting: time

Aug 26 13:10:40

2024-08-26 11:10:40.729 UTC [30] LOG: checkpoint complete: wrote 83 buffers (0.5%); 0 WAL file(s) added, 0 removed, 0 recycled; write=8.392 s, sync=0.003 s, total=8.399 s; sync files=20, longest=0.002 s, average=0.001 s; distance=539 kB, estimate=30342 kB; lsn=1B/F32AB190, redo lsn=1B/F326A418

Aug 26 13:15:32

2024-08-26 11:15:32.829 UTC [30] LOG: checkpoint starting: time

Aug 26 13:15:49

2024-08-26 11:15:49.395 UTC [30] LOG: checkpoint complete: wrote 163 buffers (1.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=16.558 s, sync=0.003 s, total=16.566 s; sync files=21, longest=0.003 s, average=0.001 s; distance=1134 kB, estimate=27421 kB; lsn=1B/F3396740, redo lsn=1B/F3385CE8

Aug 26 13:20:32

2024-08-26 11:20:32.494 UTC [30] LOG: checkpoint starting: time

Aug 26 13:23:36

2024-08-26 11:23:36.560 UTC [30] LOG: checkpoint complete: wrote 1759 buffers (10.7%); 0 WAL file(s) added, 1 removed, 0 recycled; write=184.050 s, sync=0.003 s, total=184.066 s; sync files=18, longest=0.002 s, average=0.001 s; distance=14551 kB, estimate=26134 kB; lsn=1B/F59AFBB8, redo lsn=1B/F41BBA38

Solved

1 Replies

Is your Postgres in the same project as your N8N? If so, are you closing your connections properly? It doesn't seem like a platform issue with Railway so unfortunately, there is not much else the team can do on your behalf here.


Status changed to Awaiting User Response Railway over 1 year ago


Railway
BOT

6 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 6 months ago


Loading...