Yep it was indeed the hot_standby. Working now.
Thanks!
On Mon, Sep 24, 2018 at 1:06 PM David Steele <david@xxxxxxxxxxxxx> wrote:
Hi Aldo,
On 9/23/18 11:53 AM, Aldo Sarmiento wrote:
>
> # (REPLICA) tail -n 100 -f /var/log/postgresql/postgresql-9.4-main.log
> 2018-09-23 10:22:14.111 P00 INFO: unable to find
> 0000000100000CB600000053 in the archive
> 2018-09-23 10:22:14.111 P00 INFO: got WAL segment 0000000100000CB600000053
> 2018-09-23 10:22:14.111 P00 INFO: archive-get command end: aborted
> with exception [001]
This is a known issue in 2.05. It will report an error at INFO level
when a WAL segment is not found, but is otherwise harmless.
> 2018-09-23 10:27:57.129 CDT [10139-2]: bpd_production postgres@[local]
> 57P03 [unknown] FATAL: the database system is starting up
Are you sure `hot_standby=on` on the standby? I don't see it in your
configuration.
Regards,
--
-David
david@xxxxxxxxxxxxx
