Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jDDQJ-0007oz-9q for psycopg@arkaria.postgresql.org; Sat, 14 Mar 2020 20:30:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jDDQF-0004eu-SB for psycopg@arkaria.postgresql.org; Sat, 14 Mar 2020 20:30:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jDDQF-0004el-HL for psycopg@lists.postgresql.org; Sat, 14 Mar 2020 20:30:15 +0000 Received: from [64.147.123.25] (helo=wout2-smtp.messagingengine.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jDDQC-0006l8-7F for psycopg@postgresql.org; Sat, 14 Mar 2020 20:30:14 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id A9EB5646; Sat, 14 Mar 2020 16:30:00 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 14 Mar 2020 16:30:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm2; bh=U 2tY2nr5yAWDF15G0biKi81I7CiUAjSCMs3bO5RGo+A=; b=AR5nV4YDiQi+zLsaU IQ3rY4tTkFimvytd0uptVkRuitBiH14zNgrcDWkcruJK53t/d75rgkccNO4AAAMg OwugqulDn/WI6XG2eO9jdE3BbxWEW+jVRpkPCJuvfHJCCVWoOEUkV6Erwm5FQfAH iJdCdf8YUbbCGU3cGf3QXmc3TR0D69rf5dBpHyDNY7XqYwGKSFifo3Ci5I7VK2ov lOPO7yHVxEh4zG9dPEUui3F84+JFx6lpBewapdCj+mwsn6ukd4mMtBGJnOcF9l1R WWaBkek+yQDGCeHeNEyB9lkQ/pAxlQmpe1/lZfFbtni2zpj71lUvXkqa9l3Xb1Y3 JCoHw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=U2tY2nr5yAWDF15G0biKi81I7CiUAjSCMs3bO5RGo +A=; b=vGUzKvrXz7lYFT1rDXMLeKBGqD0CPBfl3khcq61PedTyPnBHLxHTlV4lg kQhochPvUlt+FWaCoJFoQg03VclNLDTWuSmeMI7lWHCRnZZa6f7QIWnGkBcFjQFW Z1Tx1FZbH+gVObkZQl3MHEgtFcIY3rUUnX4+7FKCHaKWlzCfpO79o+laV8OEKIDk Si+Gpkysb/6aS4BV1ED0MP+wooYX/fxtbQrMFUuL0KbtCzfF0sPhwdJ+P9e5DEEn symT2zy/X8Huy9QRX+YOKCR+GXzR2Fw4f2qCBn6Of1akIvCinYOgD9/MSC3eZNiF m+zW8bBIvJWO4uJysb+0FA6KHTLOw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvledgudeflecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrghenucfkphepjedurddv uddvrdduvdelrdduleefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Received: from [192.168.1.10] (unknown [71.212.129.193]) by mail.messagingengine.com (Postfix) with ESMTPA id 97B983280063; Sat, 14 Mar 2020 16:29:59 -0400 (EDT) Subject: Re: wire protocol errors on Debian (py3/psyco 2.8) To: Daniele Varrazzo , psycopg@postgresql.org References: <20200314153421.GC1104@hermes.hilbert.loc> From: Adrian Klaver Message-ID: Date: Sat, 14 Mar 2020 13:29:58 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 64.147.123.25 (deferred) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 3/14/20 12:35 PM, Daniele Varrazzo wrote: > > > > The error comes from the libpq failing to parse messages from the server > (at a glance CommandComplete and RowDescription - see > https://www.postgresql.org/docs/current/protocol-message-formats.html) > which are probably just the most common ones. > > I doubt it's a bug with libpq 12.2 or whatever server is on the other > side of the wire: we would have seen this error more often. If you want > to investigate in that direction you may ask core devs if there have > been changes in that area for those versions. I did run across this: https://www.postgresql.org/docs/12/release-12-2.html " Fix bugs in handling of non-blocking I/O when using GSSAPI encryption (Tom Lane) These errors could result in dropping data (usually leading to subsequent wire-protocol-violation errors) or in a “livelock” situation where a sending process goes to sleep although not all its data has been sent. Moreover, libpq failed to keep separate encryption state for each connection, creating the possibility for failures in applications using multiple encrypted database connections. " Would be nice to know what actual Postgres version is and how it is configured? > > My wild guess is either faulty network or faulty memory on the machine, > most likely the latter. > > -- Daniele -- Adrian Klaver adrian.klaver@aklaver.com