Postgres logs "could not receive data from client: Connection reset by peer" when TLS is enabled

When enabling TLS connections for Postgres as documented here Configuring PostgreSQL TLS, the DB container logs:

LOG: could not receive data from client: Connection reset by peer

There’s no impact about this log, however, you may want to understand why this is repeatedly logged.

This is an expected normal behavior. The reason why it happens is because Kong maintains a connection pool with Postgres, and the default timeout is 60 seconds, which is controlled by the pg_keepalive_timeout parameter. When a connection in the pool times out, it will be released. If TLS is enabled on that connection, the underlying Nginx that Kong depends on will send an RST packet to quickly close TLS when closing the connection. The RST packet caused Postgres to detect that Kong reset the connection and therefore output a log.

You can also adjust the pg_keepalive_timeout to a very large value, such as 500 seconds, to suppress the disconnection errors overrunning your logging systems, but it is not necessary from Kong’s side. Alternatively, you can disable the connection logs in Postgres (which is off by default) according to the Postgres documentation on log_disconnections.

Related documentation:

• Kong Configuration Reference: Postgres Settings