Re: BUG #14320: systemd terminates postgresql hot standby instance 90 seconds after start

From: Andreas Papst <andreas(dot)papst(at)univie(dot)ac(dot)at>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14320: systemd terminates postgresql hot standby instance 90 seconds after start
Date: 2016-09-15 06:28:02
Message-ID: 57DA3F72.4010408@univie.ac.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello,

On 09/15/2016 02:19 AM, Peter Eisentraut wrote:
> Something unusual is going on. Try running the commands in the unit
> file by hand and see whether they succeed or print additional
> diagnostics. Check the systemd logs, if any. The reason the process
> ends up getting killed is that systemd thinks it has not started
> successfully.
>
yeah, when systemd's startup process is running into it's timeout
it terminates postgres process. If I change the timeout threshold
to unlimited, postgres operates for ever.
And as I wrote, when I send Postgres a signal, i.e. `systemctl reload
postgresql´, postgres process detaches, the blocked startup script
is freed and returns success to systemd.

No more logs are available.

Thanks
Andreas
--
________________________________________________________________________
Andreas Papst |
Vienna University Computer Center | E-Mail: andreas(dot)papst(at)univie(dot)ac(dot)at
Universitaetsstrasse 7 | Phone: +43 1 4277 / 140 36
A-1010 Vienna, Austria, Europe | Fax.: +43 1 4277 / 8 140 36

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Huan Ruan 2016-09-15 08:32:16 Re: BUG #14319: Logical decoding dropping statements in subtransactions
Previous Message Bhupendra Kumar 2016-09-15 06:22:01 Facing issue with Global lock in postgres-bdr