From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Postgres 10.1 fails to start: server did not start in time |
Date: | 2017-11-10 20:32:18 |
Message-ID: | CAMjNa7e6O-ng7xi38bWOwz3d67U1bkDo3k480kyNv10rwErogQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hey all,
I am in the process of upgrading to Postgres 10, and am having trouble
getting my streaming replica working.
OS: Debian 9.2
Version: 10.1
I have my primary backed up using pgbackrest, and I restore that to my
replica. It generates a recovery.conf which has a restore command for
the WAL to pull them from the pgbackrest server.
The recovery succeeds, but when I go to start the cluster on the
standby, it begins to replay the WAL, and does so for about 30
seconds. Then I get a line in my log saying:
> pg_ctl: server did not start in time
Followed by:
> 2017-11-10 20:27:35.907 UTC [7132] LOG: received smart shutdown request
> ERROR [063]: : terminated on signal [SIGTERM]
> 2017-11-10 20:27:35.911 P00 INFO: archive-get command end: terminated on signal [SIGTERM]
ERROR [063]: : terminated on signal [SIGTERM]
> 2017-11-10 20:27:35.912 P00 INFO: archive-get command end: terminated on signal [SIGTERM]
> 2017-11-10 20:27:35.978 UTC [7142] LOG: shutting down
> 2017-11-10 20:27:36.151 UTC [7132] LOG: database system is shut down
This happens weather I have the server configured as a standby or not.
Any help would be very appreciated.
Thanks,
-Adam
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-11-10 20:51:52 | Re: Postgres 10.1 fails to start: server did not start in time |
Previous Message | Paul Jungwirth | 2017-11-10 17:26:54 | Re: archive_command not being executed |