Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ejsQM-0000ku-L9 for pgsql-admin@arkaria.postgresql.org; Thu, 08 Feb 2018 20:04:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ejsQL-0004V1-0f for pgsql-admin@arkaria.postgresql.org; Thu, 08 Feb 2018 20:04:01 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ejsQK-0004Ur-Ku for pgsql-admin@lists.postgresql.org; Thu, 08 Feb 2018 20:04:00 +0000 Received: from tamriel.snowman.net ([2001:470:e38f::11]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ejsQI-00085g-68 for pgsql-admin@postgresql.org; Thu, 08 Feb 2018 20:03:59 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id A1B305F79C; Thu, 8 Feb 2018 15:03:57 -0500 (EST) Date: Thu, 8 Feb 2018 15:03:57 -0500 From: Stephen Frost To: "David G. Johnston" Cc: rammohan ganapavarapu , pgsql-admin@postgresql.org Subject: Re: incomplete startup packet Message-ID: <20180208200357.GE2416@tamriel.snowman.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Rf6DP7gcEU1dbx/5" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Rf6DP7gcEU1dbx/5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * David G. Johnston (david.g.johnston@gmail.com) wrote: > On Thu, Feb 8, 2018 at 10:16 AM, rammohan ganapavarapu < > rammohanganap@gmail.com> wrote: > > I am seeing lot of these* "incomplete startup packet" *messages in > > postgresql.log in 9.6 version, what does it mean? some thing wrong with > > server? > > =E2=80=8BIt means that some piece of software is trying, incorrectly, to = connect to > PostgreSQL=E2=80=8B. The server is probably just fine but you should pro= bably hunt > down the other side of the connections and see what is wrong there - or > block them if the other end isn't something you want trying to connect to > your database. These might be entirely reasonable checks to see if the service is up and running from monitoring systems. That's certainly not unheard of and it'd actually be nice if we had a way to avoid having these errors get thrown in that case. Even better would be making the monitoring systems smarter, but that's not always easily done. Thanks! Stephen --Rf6DP7gcEU1dbx/5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJafK0tAAoJEO1sijiDR2RVpzcQAIzmp4fBuoiikeekY+xfsgOQ lB8LRWG5T9J4lsQ0ylyGIzhftX/L2hQvAqPWOe+9gPLrFCGwzfV1mJqHsVvIVDUG bwcoWfUMWivHLd2z2exR0RgUfY4uAze+tPRbROC8Ny95UCrV1jJ/QA+vgGa9z9Af ZhAYFU5lFxTsTF0Imw4SfTjoX6mvXh9XgBQR2INX0OCtgUTmG7GEQ+5YWKkC+RdU FIVCzRIyqJdD/XPfvFg8HeeSnaIU4+nha//Gk9fkjFxCF9dgutXbiiTvPEwKz9pT WShwgt+TYynqdSaHrrOyV2mbii7mUHEt9XjSXYCBc1wI337HLNHuSjQabqrKxbsS bVmi8jXBx69q9QLluCTzIekHHHpNuDRw1hjKwqEhdCbxBH0n6DOxV8YPjudoSfAh 2kFaegON8s7MLrl2wBpJ0ppVm26cUBUN8ZoJqDRy1N+vY4wTWTkOrqNIlrrd/3wJ MVA6/TDdxok9bBT8tLmhAo2nuBmbB1/DPdaRSmu3zAH7proLG0+66Rdu9FE1IkwS oEPpi+6SKxdiBLHptwb20RXfPSYuTritpo8bYLpPUThKsojNkU3WUvP8HN+BveBY liwYeYkKGTCYyC9Qw2ZPDzYHfq6YHtk1kBGzPSAPjnjKr+XKs1xtIiCDZPfjF1pV OrlqM7pb7V1shRO+qujl =QJ/P -----END PGP SIGNATURE----- --Rf6DP7gcEU1dbx/5--