Re: streaming replication timeout error - Mailing list pgsql-general

From Adrian Klaver
Subject Re: streaming replication timeout error
Date
Msg-id 52555DA5.7010104@gmail.com
Whole thread Raw
In response to streaming replication timeout error  (高健 <luckyjackgao@gmail.com>)
Responses Re: streaming replication timeout error
List pgsql-general
On 10/08/2013 07:58 PM, 高健 wrote:
> Hello:
>
> My customer encountered some connection timeout, while using one
> primary-one standby streaming replication.
>
> The original log is japanese, because there are no error-code like
> oracle's ora-xxx,
> I tried to translate the japanese information into English, But that
> might be not correct English for PG.
>
>
> The most important part is:
>
> 2013-09-22 09:52:47 JST[28297][51d1fbcb.6e89-2][0][XX000]FATAL:  Could
> not receive data from WAL stream: could not receive data from server:
> connection timeout
> scp: /opt/PostgresPlus/9.2AS/data/arch/000000AC000001F10000004A: No such
> file or directory
>
> I was asked about:
> In what occasion will the above fatal error occur?
>
> I looked into the postgresql.conf file for the primary and standby server.
> And made some experiences.
>
> I found:
> Senario I:
>
> If the wal file wanted is removed manually:
>
> Both in primary and standby, log will be like this:
> FATAL:  could not receive data from WAL stream: FATAL:  requested WAL
> segment 000000010000000000000011 has already been removed
>
>

>
> But I haven't found a  good explanation fitting the logs' FATAL error.
> Can anybody give me some info?

Would seem to me the interesting part is:

  scp: /opt/PostgresPlus/9.2AS/data/arch/000000AC000001F10000004A: No
such  file or directory

Are using scp to move WAL files to an archive directory?

If so, it seems scp is having issues, either network interruption or the
file is disappearing under it.

>
> Thanks in advance
>
> jian gao
>


--
Adrian Klaver
adrian.klaver@gmail.com


pgsql-general by date:

Previous
From: janek12@web.de
Date:
Subject: Re: pg_similarity
Next
From: Jesse Long
Date:
Subject: Re: Incorrect index being used