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 1jD92D-00047Z-6R for psycopg@arkaria.postgresql.org; Sat, 14 Mar 2020 15:49:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jD92B-0003Sl-J8 for psycopg@arkaria.postgresql.org; Sat, 14 Mar 2020 15:49:07 +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 1jD92B-0003Se-8D for psycopg@lists.postgresql.org; Sat, 14 Mar 2020 15:49:07 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jD929-0004gk-4I for psycopg@postgresql.org; Sat, 14 Mar 2020 15:49:06 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id B16F75F8 for ; Sat, 14 Mar 2020 11:49:03 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 14 Mar 2020 11:49:03 -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=k yo/pu8lDfuyLZP9SM6o2lPk5RCWELOMEdrT25SV4AM=; b=f/MWukIOiQmHj69Y/ vK0ui4Kzbx2GMxjCs6F5UE47e3Q2n6iuh0OwcEn+ZBhwU9VxGmUvE305NaPRwUvu KrYOVzGhIDdO5fjgaP3v22Sp27Pai6co0d8WO/cC6JyNV5rzaRozEMa9AJlxDCN4 PpFw+XFJOiRwSSjM27d3NBQxlUX5S13Z7KQTquVIrfqbJKfJ0KnCcqhr0I4Xx8q3 UEML1ms990aX/D4FQePHzq/Lbo4XvavLshKFXlMo4EqL4xYeuUNPrX8WTfjdKDmQ 3IEJdgqRLXpXEC6pfWUaDpbRdjkLI9mcjz4Rvfi2orCspuZLf6riitxyhXNxE26R F7NMw== 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=kyo/pu8lDfuyLZP9SM6o2lPk5RCWELOMEdrT25SV4 AM=; b=YwWp9Uecd5GhvqvozApgi/hEBgDWMmBg8Rsbasr19q2JkA8KIRsyZ/21w zX7s1h6pZipMzC39wQKJb+uyqUfNX2ZX6J4ZX0zlHtWOM5H/BH8A2+4WIm9tZuRQ 3/HXx5bI/cfcPNpueMDj16vtZ9/7joYLIjw66vzLOvJ1xiwA7aP8kwlxN8WSCwdz dITtBVB+c28LFXziAD7S2tGDFCHSw5kIq9dGEv8H5FTtxqH/LDzCcxFKeB2Es06m mUoUCHUBCAeg6Mv84wFQUTLFbOUH0fbOyte/x689ogUdt8AUPytHMM8HnJuCFkB8 BRO3GSuNcrQm8jjQUuzQvPsmWp3Jg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvledgkedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtke ertddtfeehnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecukfhppeejuddrvdduvddruddvledrud elfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegr ughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Received: from [192.168.1.10] (unknown [71.212.129.193]) by mail.messagingengine.com (Postfix) with ESMTPA id C27B13061363 for ; Sat, 14 Mar 2020 11:49:02 -0400 (EDT) Subject: Re: wire protocol errors on Debian (py3/psyco 2.8) To: psycopg@postgresql.org References: <20200314153421.GC1104@hermes.hilbert.loc> From: Adrian Klaver Message-ID: <1e6ef8fb-1efd-ab1b-7dae-a880b5d53ee0@aklaver.com> Date: Sat, 14 Mar 2020 08:49:01 -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: <20200314153421.GC1104@hermes.hilbert.loc> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 3/14/20 8:34 AM, Karsten Hilbert wrote: > Hi all, > > we have two reports for psycopg2 2.8 under Python 3 on Debian > showing a problem with the wire protocol (full logs appended): > > psycopg2.OperationalError: datos insuficientes en el mensaje «T» > > or > > psycopg2.DatabaseError: el contenido del mensaje no concuerda con el largo, en el mensaje tipo «C» > > The error happens at different times when running the same > code. The versions involved: > > psycopg2 module version: 2.8.4 (dt dec pq3 ext lo64) > PostgreSQL via DB-API module "": API level 2.0, thread safety 2, parameter style "pyformat" > libpq version (compiled in): 120000 > libpq version (loaded now) : 120002 > > Platform: uname_result(system='Linux', node='Epigen7', release='5.4.0-4-amd64', version='#1 SMP Debian 5.4.19-1 (2020-02-13)', machine='x86_64', processor='') > > Python 3.7.6 (default, Jan 19 2020, 22:34:52) <\n>[GCC 9.2.1 20200117] on linux (posix) > > lsb_release: {'ID': 'Debian', 'OS': 'GNU/Linux', 'DESCRIPTION': 'Debian GNU/Linux bullseye/sid', 'RELEASE': 'testing', 'CODENAME': 'bullseye'} > > threading: sys.thread_info(name='pthread', lock='semaphore', version='NPTL 2.29') > > We don't yet know the exact version of PostgreSQL this is > running against but it is likely 12.2-1+b1 from > Debian/Unstable. > > Any ideas or hints what to look at next ? How was psycopg2 installed? What is the code being run when the errors are thrown? > > Thanks, > Karsten > -- > GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B > -- Adrian Klaver adrian.klaver@aklaver.com