Re: streaming replication: could not receive data from client: Connection reset by peer

Поиск
Список
Период
Сортировка
От Albe Laurenz
Тема Re: streaming replication: could not receive data from client: Connection reset by peer
Дата
Msg-id A737B7A37273E048B164557ADEF4A58B17C4FAB2@ntex2010i.host.magwien.gv.at
обсуждение исходный текст
Ответ на streaming replication: could not receive data from client: Connection reset by peer  (Anson Abraham <anson.abraham@gmail.com>)
Ответы Re: streaming replication: could not receive data from client: Connection reset by peer  (Anson Abraham <anson.abraham@gmail.com>)
Список pgsql-general
Anson Abraham wrote:
> I'm on Debian Wheezy running postgres 9.3
> 
> both boxes are identical.
> 
> I see in log file on slaves:
>  LOG:  could not receive data from client: Connection reset by peer

That looks to me like a client that is connected to the slave
is dying.

Do you have hot standby turned on?

Are there any other messages on master or slave around this time?

Does this message come right away whan you start the slave or only
after a certain time?

> OpenSSL is the same version on master and slaves.  The libssl is also too.

Do you use SSL for streaming replication?

What connection options does the slave use to connect to the master?

> I set ssl_renegotiation=0.  So not sure why i'm seeing this in the logs on my slave environments.
> doing research (aka googling), i see that everyone says to set ssl_renegotiation=0 but already done
> that.  also mentions of libssl library / OpenSSL could be different versions, but that's not the case
> either.

That would help if you have a renegotiation problem, i.e.
streaming replication has a problem after a time of correct operation.

Yours,
Laurenz Albe

В списке pgsql-general по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Links in docs broken
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: pg_dump doesn't restore on newer database due to schema issues (bug or limitation?)