From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ram DBA <postgresdbas@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Frequent errors in postgresql.log
Date: Mon, 12 Dec 2016 18:56:19 -0500
Message-ID: <16608.1481586979@sss.pgh.pa.us> (raw)
In-Reply-To: <CAGb7rSGvALECJYLp8PaO9QrXc5Mz1jFaSMEVd4_H6jv_Z5dqXA@mail.gmail.com>
References: <CAGb7rSGvALECJYLp8PaO9QrXc5Mz1jFaSMEVd4_H6jv_Z5dqXA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Ram DBA <postgresdbas@gmail.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@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, postgresdbas@gmail.com
Subject: Re: Frequent errors in postgresql.log
In-Reply-To: <16608.1481586979@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox