Re: Frequent errors in postgresql.log

On Mon, Dec 12, 2016 at 6:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Ram DBA <postgresdbas(at)gmail(dot)com> writes:
> > There are frequent errors in our postgresql.log.
> > Though they aren't harmful to the database, would like to understand the
> > cause of it.
>
> > < 2016-12-12 15:29:09.036 PST >LOG: incomplete startup packet
> > < 2016-12-12 15:30:09.037 PST >LOG: incomplete startup packet
> > < 2016-12-12 15:31:09.037 PST >LOG: incomplete startup packet
>
> Something's scanning your postmaster port once a second, ie, opening
> a connection and then closing it without sending anything. If you
> don't have a monitoring system that's supposed to be doing that,
> it would behoove you to find out where that traffic is coming from.
>
> regards, tom lane
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

Recommend making your log_line_prefix more informative so you can get some
additional information about the connection attempts. This is the standard
one I use

log_line_prefix = '%t [%r] [%p]: [%l-1] user=%u,db=%d,e=%e '

The standard postgresql.conf file comes with an explanation for what all
these special values mean as well as more available. You will have to
reload the config to put it into affect. Just run this as a superuser:
SELECT pg_reload_conf();

Keith