From: | Christoph Berg <myon(at)debian(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adam Brusselback <adambrusselback(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres 10.1 fails to start: server did not start in time |
Date: | 2017-11-11 13:23:54 |
Message-ID: | 20171111132354.esi73rlpq3goyrqh@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Re: Tom Lane 2017-11-10 <8027(dot)1510347112(at)sss(dot)pgh(dot)pa(dot)us>
> > 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
Hi Adam,
how did you start the server? Via pg_ctlcluster, the init system, or
directly via pg_ctl?
> > Followed by:
> >> 2017-11-10 20:27:35.907 UTC [7132] LOG: received smart shutdown request
> >> ERROR [063]: : terminated on signal [SIGTERM]
>
> ... pg_ctl itself wouldn't decide to forcibly shut down the server
> if the timeout expired. It merely stops waiting and tells you so.
> It seems like this must represent misdesign of whatever start script
> you're using. I think you need to complain to the Debian packagers
> about that.
pg_ctlcluster doesn't shut down if startup fails, but to be sure, we'd
need to see the full log of whatever initiated the startup. If you are
using systemd, what does `systemctl status postgresql(at)10-main` report?
If that doesn't have anything, also check journalctl.
Christoph
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2017-11-11 13:28:05 | Re: pg on Debian servers |
Previous Message | rob stone | 2017-11-11 13:23:46 | Re: pg on Debian servers |