| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgBackRest : "ERROR: [042]: unexpected EOF reading line from remote process on" and stale pgbackrest processes hanging |
| Date: | 2019-01-17 06:50:27 |
| Message-ID: | 5dca01e0-0cd9-2064-571f-473e97b82087@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 1/16/19 10:27 PM, Stephen Frost wrote:
> * Achilleas Mantzios (achill(at)matrix(dot)gatewaynet(dot)com) wrote:
>>
>> Is this behavior normal ? Would the 4 processes be killed due to KEEPALIVE settings eventually ?
>
> Yes, they almost certainly would have timed out eventually- but how
> long were you already waiting..? The timeouts in pgbackrest are not
> terribly long, in general.
By default the remote processes will shutdown after 30 minutes if they
have not gotten a message from the main process. This is controlled by
the `protocol-timeout` option.
It's a bit unusual for them to get stuck like this -- usually they get
an eof and exit immediately. Definitely looks like something was up
with SSH.
Regards,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabio Pardi | 2019-01-17 08:32:41 | Re: archive command failed with exit code 1 |
| Previous Message | Achilleas Mantzios | 2019-01-17 05:20:27 | Re: pgBackRest : "ERROR: [042]: unexpected EOF reading line from remote process on" and stale pgbackrest processes hanging |