Subject: Re: pgBackRest : "ERROR: [042]: unexpected EOF reading line from
 remote process on" and stale pgbackrest processes hanging
To: Stephen Frost <sfrost@snowman.net>,
 Achilleas Mantzios <achill@matrix.gatewaynet.com>
Cc: pgsql-admin@lists.postgresql.org
References: <e7d0ac3f-cf49-7d04-87b7-0944a46207e0@matrix.gatewaynet.com>
 <20190116202758.GG2528@tamriel.snowman.net>
From: David Steele <david@pgmasters.net>
Message-ID: <5dca01e0-0cd9-2064-571f-473e97b82087@pgmasters.net>
Date: Thu, 17 Jan 2019 08:50:27 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0)
 Gecko/20100101 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <20190116202758.GG2528@tamriel.snowman.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/16/19 10:27 PM, Stephen Frost wrote:
> * Achilleas Mantzios (achill@matrix.gatewaynet.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@pgmasters.net