Re: FATAL: could not receive data from WAL stream - Mailing list pgsql-general

From Patrick B
Subject Re: FATAL: could not receive data from WAL stream
Date
Msg-id CAJNY3iuUgNq-D0P3kAhaz1rpYXw0t0EV5h9Nst5uHYWJ67YeQw@mail.gmail.com
Whole thread Raw
In response to Re: FATAL: could not receive data from WAL stream  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-general


2016-09-20 16:46 GMT+12:00 Michael Paquier <michael.paquier@gmail.com>:
On Tue, Sep 20, 2016 at 1:30 PM, Patrick B <patrickbakerbr@gmail.com> wrote:
> 2016-09-20 15:14 GMT+12:00 Venkata B Nagothi <nag1010@gmail.com>:
>> Do you mean to say that the WAL file "000000020000179A000000F8" is
>> available @ "/var/lib/pgsql/9.2/archive" location ?
>
> Yes!

Timeline 2 has visibly reached its end at segment
000000020000179A000000F8 and it cannot find in the archive the history
file to see from which timeline it needs to fetch afterwards. As the
timeline file cannot be found, it then attempts to fetch the segment
that it thinks is complete from the master itself.

Didn't you trigger a promotion which would make the master reach the
timeline 3? And are you sure that 00000003.history is not in the
archives?
--
Michael



The server went down and when it came back online I got that errors.. 


I got some errors on the logs: systemd1: Removed slice User Slice of postgres.

I belive something happened with Postgres user and when the server came back online it started postgres in a new path... that excluded recovery.conf and the server might have been promoted as master

This means I'll have to re-build the DB right?

Patrick

pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: FATAL: could not receive data from WAL stream
Next
From: Adrian Klaver
Date:
Subject: Re: We have a requirement to downgrade from PostgreSQL 9.5.4 to 9.5.2