Re: ssl3 errors in replication.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mario Splivalo <mario(dot)splivalo(at)megafon(dot)hr>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: ssl3 errors in replication.
Date: 2012-02-02 16:16:14
Message-ID: 25074.1328199374@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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).

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mario Splivalo 2012-02-02 16:24:09 Re: ssl3 errors in replication.
Previous Message Mario Splivalo 2012-02-02 16:15:58 Re: ssl3 errors in replication.