Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jda3X-0003IS-Mh for pgsql-bugs@arkaria.postgresql.org; Tue, 26 May 2020 13:55:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jda3W-0007mA-Ke for pgsql-bugs@arkaria.postgresql.org; Tue, 26 May 2020 13:55:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jda3V-0007lf-SL for pgsql-bugs@lists.postgresql.org; Tue, 26 May 2020 13:55:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jda3T-0003xT-MC for pgsql-bugs@lists.postgresql.org; Tue, 26 May 2020 13:55:44 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 04QDtgqc015836; Tue, 26 May 2020 09:55:42 -0400 From: Tom Lane To: rcastro@stratio.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16463: Sporadic SSL handshake failures in Windows client In-reply-to: <16463-81778942ee95cdfc@postgresql.org> References: <16463-81778942ee95cdfc@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 26 May 2020 13:18:53 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <15834.1590501342.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Tue, 26 May 2020 09:55:42 -0400 Message-ID: <15835.1590501342@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > We are connecting to a Postgres-XL server from a SQL Server Integration > Services (SSIS, from now) using an OLEDB driver solution developed by > Intellisoft. The PostgresXL server is deployed in a Centos 7 machine with a > PGBouncer pool. > Monthly, we are facing an issue that consists in connection failures between > SSIS and PGBouncer. The pooler is showing the following error: > ssl3_get_client_certificate:peer did not return a certificate > PGBouncer is rejecting the connection, so PostgresXL server is never > reached. In order to resolve this issue, we have to reinstall the PostgresXL > certificates in the Windows Server. After that, the connection can be > reestablished without any server interventions. Weird ... but I'm afraid you have come to the wrong place for help. This mailing list deals with PG server bugs, and the server seems to be the one component that is clearly not at fault in your case. It could be PGBouncer's fault, so I'd suggest inquiring through their support contact. (I do not know offhand what that is, but it's not here.) But TBH, if reinstalling the identical certificates on the client machine makes the problem go away, it's hard to conclude that it's not a client-side bug. regards, tom lane