Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1exXKh-0005Id-Em for pgsql-admin@arkaria.postgresql.org; Sun, 18 Mar 2018 12:22:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1exXKf-0003ji-E7 for pgsql-admin@arkaria.postgresql.org; Sun, 18 Mar 2018 12:22:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1exXKf-0003jZ-6s for pgsql-admin@lists.postgresql.org; Sun, 18 Mar 2018 12:22:37 +0000 Received: from relay1-d.mail.gandi.net ([217.70.183.193]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1exXKc-00058O-7t for pgsql-admin@lists.postgresql.org; Sun, 18 Mar 2018 12:22:36 +0000 X-Originating-IP: 80.201.109.203 Received: from [172.16.2.122] (unknown [80.201.109.203]) (Authenticated sender: marco.mailbox@debooy.eu) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 13528240003 for ; Sun, 18 Mar 2018 13:22:31 +0100 (CET) Subject: Re: Barman backup fails after upgrade to PostgreSQL 10 To: pgsql-admin@lists.postgresql.org References: <0299b66f-c7ef-1c64-4e7f-9dc7d4d4c3a3@debooy.eu> From: Marco DE BOOIJ Message-ID: <13a222d4-0fa9-6c74-ea8a-92010b565a4b@debooy.eu> Date: Sun, 18 Mar 2018 13:22:31 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: nl-BE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 >