From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Alexey Klyukin <alexk(at)hintbits(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Valentine Gogichashvili <valgog(at)gmail(dot)com> |
Subject: | Re: recurring SSL errors with streaming replication in 9.4.1 |
Date: | 2015-02-19 11:12:20 |
Message-ID: | 20150219111220.GH16383@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On 2015-02-19 12:07:19 +0100, Alexey Klyukin wrote:
> We are getting period FATALs from our recently upgraded to 9.4.1 Hot Standby:
I could reproduce similar things with earlier version as well..
> 015-02-17 03:01:26.251 CET,,,30247,,54e1bfe0.7627,2,,2015-02-16
> 11:01:04 CET,,0,FATAL,XX000,"could not send data to WAL stream: SSL
> error: unexpected record
> ",,,,,,,,,""
Check out
http://archives.postgresql.org/message-id/20150126101405.GA31719%40awork2.anarazel.de
, especially Heikki's answer + patches.
> ssl_renegotiation_limit is to the default of '512MB'. I will disable
> it on one of the clusters and see if the problem is still there, but
> meanwhile, is there anything we can provide to help resolve this
> issue? I see in the release notes for 9.4 that the SSL renegotiation
> code has been improved, but apparently some issues are still there.
Yea :(.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | 2015-02-19 14:31:26 | Re: Fwd: Data corruption after restarting replica | |
Previous Message | Alexey Klyukin | 2015-02-19 11:10:08 | Re: recurring SSL errors with streaming replication in 9.4.1 |