Hello, SSL renegotiation is error prone in PostgreSQL version 9.3 and below. You can either upgrade your PostgreSQL server or as a work around ,if network security is not your major concern SSL renegotiation parameter can be switched off to avoid connection lost errors due to SSL renegotiation.
On Tue, Jun 3, 2014 at 5:16 PM, Mithun Kumar <mithunsi...@gmail.com> wrote: > Hi, > > Currently i working on a scenario where client uses openssl for connecting > to PostgreSQL server. > > There is a flag in Server which invokes SSL renegotiation after certain > amount of data is transferred. > > Connection terminates as part of SSL_read() with Errno = 10054 ( (An > existing connection was forcibly closed by the remote host.) > > Server logs shows following:- > 2014-06-03 06:31:41 EDT FATAL: connection to client lost > 2014-06-03 07:12:05 EDT LOG: SSL renegotiation failure > 2014-06-03 07:12:05 EDT LOG: SSL failed to send renegotiation request > 2014-06-03 07:12:05 EDT LOG: SSL error: unsafe legacy renegotiation > disabled > > > Any pointers? :) >
