pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedFrequent errors in postgresql.log
4+ messages / 4 participants
[nested] [flat]
* Frequent errors in postgresql.log
@ 2016-12-12 23:35 Ram DBA <postgresdbas@gmail.com>
0 siblings, 2 replies; 4+ messages in thread
From: Ram DBA @ 2016-12-12 23:35 UTC (permalink / raw)
To: pgsql-admin
Hi team,
I am new to PostgreSQL world, so please help in understanding below issue.
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
Thank you,
Ram
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Frequent errors in postgresql.log
@ 2016-12-12 23:55 David G. Johnston <david.g.johnston@gmail.com>
parent: Ram DBA <postgresdbas@gmail.com>
1 sibling, 0 replies; 4+ messages in thread
From: David G. Johnston @ 2016-12-12 23:55 UTC (permalink / raw)
To: Ram DBA <postgresdbas@gmail.com>; +Cc: pgsql-admin
On Mon, Dec 12, 2016 at 4:35 PM, Ram DBA <postgresdbas@gmail.com> wrote:
> Hi team,
>
> I am new to PostgreSQL world, so please help in understanding below issue.
>
> 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
>
>
A quick search, navigated to via SO, turned up an email I sent a long
while ago. There seems to be lots of other questions on the same topic.
http://postgresql.nabble.com/Incomplete-startup-packet-help-needed-td5199030.html
In short, some piece of client software isn't playing nicely with
PostgreSQL.
David J.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Frequent errors in postgresql.log
@ 2016-12-12 23:56 Tom Lane <tgl@sss.pgh.pa.us>
parent: Ram DBA <postgresdbas@gmail.com>
1 sibling, 1 reply; 4+ messages in thread
From: Tom Lane @ 2016-12-12 23:56 UTC (permalink / raw)
To: Ram DBA <postgresdbas@gmail.com>; +Cc: pgsql-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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Frequent errors in postgresql.log
@ 2016-12-13 03:24 Keith <keith@keithf4.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Keith @ 2016-12-13 03:24 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Ram DBA <postgresdbas@gmail.com>; pgsql-admin
On Mon, Dec 12, 2016 at 6:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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
>
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
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2016-12-13 03:24 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2016-12-12 23:35 Frequent errors in postgresql.log Ram DBA <postgresdbas@gmail.com>
2016-12-12 23:55 ` David G. Johnston <david.g.johnston@gmail.com>
2016-12-12 23:56 ` Tom Lane <tgl@sss.pgh.pa.us>
2016-12-13 03:24 ` Keith <keith@keithf4.com>
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