Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime

Поиск
Список
Период
Сортировка
От Christoph Berg
Тема Re: [GENERAL] Postgres 10.1 fails to start: server did not start intime
Дата
Msg-id 20171111132354.esi73rlpq3goyrqh@msg.df7cb.de
обсуждение исходный текст
Ответ на Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [GENERAL] Postgres 10.1 fails to start: server did not start in time  (Adam Brusselback <adambrusselback@gmail.com>)
Список pgsql-general
Re: Tom Lane 2017-11-10 <8027.1510347112@sss.pgh.pa.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@10-main` report?
If that doesn't have anything, also check journalctl.

Christoph


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

В списке pgsql-general по дате отправления:

Предыдущее
От: rob stone
Дата:
Сообщение: Re: [GENERAL] pg on Debian servers
Следующее
От: Christoph Berg
Дата:
Сообщение: Re: [GENERAL] pg on Debian servers