Reserved.

Hi!

I am seeing a lot of these errors in the logs: 2025-01-27 10:18:32.368 UTC [1] LOG C-0x55b0465c4c30: railway/postgres@100.64.0.9:38968 closing because: client unexpected eof (age=472s).

Is this normal?

Queries seem to work well.

Thnks!

That would be unrelated to the template, it's likely just your client not gracefully closing the connection to Pgbouncer.

Hi! We have only deployed the image as it is and conducted tests through pgBouncer. Without connecting to the bouncer, these messages appear in the log. Is there any way to manage PgBouncer and see what is really happening? Thank you.

2025-01-28 06:00:01.285 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 1 B/s, out 2 B/s, xact 877 us, query 877 us, wait 446 us

2025-01-28 06:01:01.285 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:02:01.285 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:03:01.286 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:04:01.281 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:05:00.359 UTC [1] LOG C-0x55b7cf264ef0: railway/postgres@[fd12:15da:107b:0:4000:17:6847:f919]:46452 closing because: client close request (age=599s)

2025-01-28 06:05:00.495 UTC [1] LOG C-0x55b7cf264ef0: railway/postgres@[fd12:15da:107b:0:4000:17:6847:f919]:53236 login attempt: db=railway user=postgres tls=no replication=no

2025-01-28 06:05:01.284 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 2 B/s, out 1 B/s, xact 730 us, query 730 us, wait 330 us

2025-01-28 06:06:01.281 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:07:01.287 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:08:01.287 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:09:01.288 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

2025-01-28 06:10:01.287 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 1 B/s, out 2 B/s, xact 1132 us, query 1132 us, wait 619 us

2025-01-28 06:11:01.286 UTC [1] LOG stats: 0 xacts/s, 0 queries/s, 0 client parses/s, 0 server parses/s, 0 binds/s, in 0 B/s, out 0 B/s, xact 0 us, query 0 us, wait 0 us

I'm really sorry, while I do maintain the template for Railway, I cannot provide support for the software itself.