pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marco DE BOOIJ <marco.maillist@debooy.eu>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Barman backup fails after upgrade to PostgreSQL 10
Date: Sun, 18 Mar 2018 13:22:31 +0100
Message-ID: <13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu> (raw)
In-Reply-To: <ffb937e8-a897-cb9a-6efb-6920407ee67f@silentrunner.de>
References: <0299b66f-c7ef-1c64-4e7f-9dc7d4d4c3a3@debooy.eu>
	<ffb937e8-a897-cb9a-6efb-6920407ee67f@silentrunner.de>

Dear Georg,

Many thanks for your help. I changed the max_wal_senders to 10 and 
restarted the database. Since I have a small server I did not want to 
put it higher then mentioned in the documentation of Barman 2.3. Thought 
I did not need to. Now the backup is made (took 4 minutes).

Kind regards,

Marco


Op 18-03-18 om 12:54 schreef Georg H.:
> Hello Marco,
>
>
> Am 18.03.2018 um 12:21 schrieb Marco DE BOOIJ:
>> After my upgrade of PostgreSQL 9.6 to 10.3 the backups through barman 
>> fails. There is not much data change in the database but I still do 
>> not want to loose the data. I have verified the configuration and all 
>> seems correct for Barman and PostgreSQL . I have tried to find the 
>> answer on the internet but I was not able to find it. Both Barman and 
>> PostgreSQL run on the same server.
>>
> ...
>> When I run 'barman backup all' I get the following output:
>>
>> ERROR: Backup failed copying files.
>> DETAILS: data transfer failure on directory 
>> '/srv/share/backup/barman/maat/base/20180317T233002/data'
>> pg_basebackup error:
> ...
>> pg_basebackup: could not connect to server: FATAL:  number of 
>> requested standby connections exceeds max_wal_senders (currently 2)
> ....
>> maat 20180317T233002 - FAILED
>>
> Have you tried so set max_wal_senders to a higher value? iirc the 
> default value for postgresql10 is max_wal_senders = 10
>> In the barman.log there are the following lines around this message 
>> (indicated with ....):
>>
> also worth checking is your servers barman conf file 
> (/etc/barman.d/xxx.conf) which has a line at the end pointing to the 
> postgres binaries path to use.
> What means that you have to have postgresql-client package version 10 
> on your barman server and have to change your config pointing to the 
> new path.
>
> kind regards
> Georg
>





view thread (4+ messages)

Message-ID: <13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu>
Permalink:  ../13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu/
Also on:    postgresql.org/message-id/13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: marco.maillist@debooy.eu, pgsql-admin@lists.postgresql.org
  Subject: Re: Barman backup fails after upgrade to PostgreSQL 10
  In-Reply-To: <13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox