Skip site navigation (1) Skip section navigation (2)

Re: ssl3 errors in replication.

From: Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: ssl3 errors in replication.
Date: 2012-02-02 16:15:58
Message-ID: 4F2AB6BE.8030506@megafon.hr (view raw or flat)
Thread:
Lists: pgsql-admin
On 02/02/2012 05:16 PM, Tom Lane wrote:
> Mario Splivalo <mario(dot)splivalo(at)megafon(dot)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).

Is there a way I can force replication over non-ssl channel? All those
boxes are in my private network and ssl is a bit overhead there anyhow.

	Mario


In response to

Responses

pgsql-admin by date

Next:From: Tom LaneDate: 2012-02-02 16:16:14
Subject: Re: ssl3 errors in replication.
Previous:From: Mario SplivaloDate: 2012-02-02 14:40:06
Subject: Getting master host info from a slave

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group