Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 2FA841EC5BE4 for ; Thu, 2 Feb 2012 12:16:33 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RszKo-0005H6-DO for pgsql-admin@postgresql.org; Thu, 02 Feb 2012 16:16:32 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q12GGEHg025075; Thu, 2 Feb 2012 11:16:14 -0500 (EST) To: Mario Splivalo cc: "pgsql-admin@postgresql.org" Subject: Re: ssl3 errors in replication. In-reply-to: <4F2A3D03.20405@megafon.hr> References: <4F2A3D03.20405@megafon.hr> Comments: In-reply-to Mario Splivalo message dated "Thu, 02 Feb 2012 08:36:35 +0100" Date: Thu, 02 Feb 2012 11:16:14 -0500 Message-ID: <25074.1328199374@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201202/7 X-Sequence-Number: 39067 Mario Splivalo writes: > I have these errors in my log files, occurring very often: > 2012-02-02 01:05:53 CST [4103]: [2-1] user=,db= FATAL: could not > receive data from WAL stream: SSL error: sslv3 alert unexpected message Google suggests that this might be caused by version or configuration mismatches between openssl libraries on the master and slave machines. One particular thing I'm wondering about is whether your openssl libraries deal with the SSL renegotiation bug sanely (ie they've got a fix for it that's less brain-dead than breaking the connection). regards, tom lane