Barman 2.1 - Backup never end

[Alessio Gennari]

Hi there,

I'm testing Barman 2.1 streaming mode backup with a Postgres 9.5 backend. I can launch backup command and the process starts normally, but at present it finishes never.

This is the only strange message I found in log file:

2017-01-20 11:13:01,941 [25404] barman.wal_archiver INFO: No xlog segments found from streaming for prod.

I use Debian Jessie OS and I installe both Barman and Postgres from deb packages.

Anyone can help me with this issue?

Thanks in advance,

Alessio

[Alessio Gennari]

Hi newly,

during other tests, I found strange commands appended:

/usr/lib/postgresql/9.6/bin/pg_receivexlog --dbname=dbname=replication host=citrix2.redevogames.com port=xxxxx replication=true user=repmgr application_name=barman_receive_wal --verbose --no-loop --no-password --directory=/var/lib/barman/prod/streaming --slot=barman

host and port option lacks of --, application name are not recognized by pg_receivexlog.

Also in pg_basebackup I noticed the same thing:

/usr/lib/postgresql/9.6/bin/pg_basebackup --dbname=dbname=replication host=citrix2.redevogames.com port=xxxxx replication=true user=repmgr application_name=barman_streaming_backup -v --no-password

This is my configuration:

; Barman, Backup and Recovery Manager for PostgreSQL

; http://www.pgbarman.org/ - http://www.2ndQuadrant.com/

;

; Template configuration file for a server using

; only streaming replication protocol

;

[prod]

; Human readable description

description =  "Example of PostgreSQL Database (Streaming-Only)"

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; PostgreSQL connection string (mandatory)

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

conninfo = host=citrix2.redevogames.com user=postgres dbname=xxxxxxxxx port=xxxxxx password=xxxxxxxxxx

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; PostgreSQL streaming connection string

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; To be used by pg_basebackup for backup and pg_receivexlog for WAL streaming

; NOTE: streaming_barman is a regular user with REPLICATION privilege

streaming_conninfo = host=citrix2.redevogames.com user=repmgr port=15110

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; Backup settings (via pg_basebackup)

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

backup_method = postgres

;streaming_backup_name = barman_streaming_backup

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; WAL streaming settings (via pg_receivexlog)

; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

streaming_archiver = on

slot_name = barman

;streaming_archiver_name = barman_receive_wal

;streaming_archiver_batch_size = 50

; PATH setting for this server

;path_prefix = "/usr/pgsql-9.6/bin"

Is there something wrong in my config?

Thanks in advance.

Alessio

[Alessio Gennari]

Any suggestions????

[Gabriele Bartolini]

Why do you use different hosts? What does 'barman check' says?

FYI, --dbname allows to specify a connection string, not just a database name (see https://www.postgresql.org/docs/9.6/static/app-pgreceivexlog.html).

--
 Gabriele Bartolini - 2ndQuadrant Italia - Director
 PostgreSQL Training, Services and Support
 gabriele....@2ndQuadrant.it | www.2ndQuadrant.it

--
--
You received this message because you are subscribed to the "Barman for PostgreSQL" group.
To post to this group, send email to pgba...@googlegroups.com
To unsubscribe from this group, send email to
pgbarman+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/pgbarman?hl=en?hl=en-GB

---
You received this message because you are subscribed to the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pgbarman+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alessio Gennari]

Hi Gabriele,

thank for your answer.

What do you mean with "different host"?

This is the output of barman check:

barman@rayda:~$ barman check prod

Server prod:

        PostgreSQL: OK

        superuser: OK

        PostgreSQL streaming: OK

        wal_level: OK

        replication slot: OK

        directories: OK

        retention policy settings: OK

        backup maximum age: OK (no last_backup_maximum_age provided)

        compression settings: OK

        failed backups: FAILED (there are 2 failed backups)

        minimum redundancy requirements: OK (have 0 backups, expected at least 0)

        pg_basebackup: OK

        pg_basebackup compatible: OK

        pg_basebackup supports tablespaces mapping: OK

        pg_receivexlog: OK

        pg_receivexlog compatible: OK

        receive-wal running: OK

        archiver errors: OK

I want not to use --dbname option, but pg_receivexlog and pg_basebackup have been launched in this manner by barman backup command. For this I am asking for help.

Thanks for your patience.

Alessio

On Saturday, 21 January 2017 10:58:12 UTC+1, Gabriele Bartolini wrote:

Why do you use different hosts? What does 'barman check' says?

FYI, --dbname allows to specify a connection string, not just a database name (see https://www.postgresql.org/docs/9.6/static/app-pgreceivexlog.html).

--
 Gabriele Bartolini - 2ndQuadrant Italia - Director
 PostgreSQL Training, Services and Support

 gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it

pgbarman+u...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/pgbarman?hl=en?hl=en-GB

---
You received this message because you are subscribed to the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pgbarman+u...@googlegroups.com.

[Alessio Gennari]

Hi Gabriele,

have any new suggestion?

Thanks in advance.

[Patryk Wlaź]

Hi, anything new on this? I have the same issue, while using streaming only backup. It lasts forever while plain pg_basebackup took me only about 5 minutes. Everything looks good in barman check.