Re: incomplete startup packet messages in logs

2018-11-01 Thread Vijaykumar Jain
Thanks Steve, It was indeed monitoring. i just had one check enabled, except the others which was not a check that queried postgres but a simple tcp port available. check-ports.rb -H localhost -p 5432 which was basically just creating a socket to check if it is is listening but not closing it.

Re: incomplete startup packet messages in logs

2018-11-01 Thread Vijaykumar Jain
i have disabled all monitoring i am aware of for postgresql. ( it is sensu/collectd/ and occasional queries via haproxy and pgbouncer) i have disabled them all. i did tcpdump (i am not a pro here), but ignored the ip6 loopback. i'll paste the output once i get again. Regards, Vijay On Thu, Nov

Re: incomplete startup packet messages in logs

2018-11-01 Thread Vijaykumar Jain
ok i enabled log_connections 2018-11-01 13:44:18 UTC LOG: connection received: host=::1 port=47574 2018-11-01 13:44:18 UTC LOG: incomplete startup packet i see this in my /etc/hosts ::1 localhost ip6-localhost ip6-loopback and host all all ::1/128 md5 in my hba,conf i'll ch

Re: incomplete startup packet messages in logs

2018-11-01 Thread Steve Atkins
> On Nov 1, 2018, at 1:27 PM, Vijaykumar Jain wrote: > > Hi Team, > > I know this is has been answered a lot on the internet wrt ignoring, > but i am unable to figure out why I get these messages in logs > "incomplete startup packet" Check which of your monitoring systems is configured to ch

incomplete startup packet messages in logs

2018-11-01 Thread Vijaykumar Jain
Hi Team, I know this is has been answered a lot on the internet wrt ignoring, but i am unable to figure out why I get these messages in logs "incomplete startup packet" I have a server running postgresql 10.5 on ubuntu16.04 i do not have any active external connections other than streaming postg