From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mario Splivalo <mario.splivalo@megafon.hr>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: ssl3 errors in replication.
Date: Thu, 02 Feb 2012 11:16:14 -0500
Message-ID: <25074.1328199374@sss.pgh.pa.us> (raw)
In-Reply-To: <4F2A3D03.20405@megafon.hr>
References: <4F2A3D03.20405@megafon.hr>
Mario Splivalo <mario.splivalo@megafon.hr> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mario.splivalo@megafon.hr
Subject: Re: ssl3 errors in replication.
In-Reply-To: <25074.1328199374@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox