Backup does not finish "ERROR: Backup failed issuing start backup command."

56 views
Skip to first unread message

Jose Manuel Valseca Echevarria

unread,
Mar 4, 2022, 2:46:46 AMMar 4
to Barman, Backup and Recovery Manager for PostgreSQL
Good morning guys. I have a backup that doesn't finish and I'm getting the following error:
Asking the PostgreSQL server to finish the backup.
ERROR: The backup failed to issue the backup start command.
DETAILS: Connection lost, reconnection not allowed

You have mail in /var/spool/mail/barman

[barman@barman02:~/etc$] barman check bidb
Server bidb:
        PostgreSQL: OK
        superuser or standard user with backup privileges: OK
        value_level: OK
        directories: OK
        retention policy settings: OK
        maximum backup age: OK (last_backup_maximum_age not provided)
        minimum backup size: OK (0 B)
        maximum wal age: OK (no last_wal_maximum_age provided)
        wal size: OK (0 B)
        compression settings: OK
        failed backups: OK (there are 0 failed backups)
        minimum redundancy requirements: OK (there are 0 backups, at least 0 expected)
        ssh: OK (PostgreSQL server)
        systemid consistency: OK
        archive_mode: OK
        archive_command: OK
        continuous archive: OK
        archiver errors: OK


[barman@barman02:~/log$] barman diagnose
[WARNING: The default backup strategy will change to 'concurrent_backup' in the future. Explicitly set 'backup_options' to silence this warning.
{
    "global": {
        "config": {
            "barman_home": "/opt/barman/backups",
            "barman_user": "barman",
            "basebackup_retry_sleep": "30",
            "basebackup_retry_times": "3",
            "compression": "bzip2",
            "configuration_files_directory": "/opt/barman/etc",
            "errors_list": [],
            "immediate_checkpoint": "true",
            "log_file": "/opt/barman/log/barman.log",
            "network_compression": "true",
            "post_backup_script": "/opt/barman/bin/backup_check.sh",
            "pre_backup_script": "/opt/barman/bin/backup_check.sh",
            "reuse_backup": "link"
        },
        "system_info": {
            "barman_ver": "2.18",
            "kernel_ver": "Linux barman02.xxx.xx 3.10.0-1160.24.1.el7.x86_64 #1 SMP Thu Apr 8 19:51:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux",
            "python_ver": "",
            "release": "LSB Version:\t:core-4.1-amd64:core-4.1-noarch\nDistributor ID:\tCentOS\nDescription:\tCentOS Linux release 7.9.2009 (Core)\nRelease:\t7.9.2009\nCodename:\tCore",
            "rsync_ver": "rsync  version 3.1.2  protocol version 31",
            "ssh_ver": "",
            "timestamp": "Fri Mar  4 08:31:30 2022"
        }
    },
    "servers": {
        "bidb": {
            "backups": {},
            "config": {
                "active": true,
                "archiver": true,
                "archiver_batch_size": 0,
                "backup_directory": "/opt/barman/backups/bidb",
                "backup_method": "rsync",
                "backup_options": "concurrent_backup",
                "bandwidth_limit": null,
                "barman_home": "/opt/barman/backups",
                "barman_lock_directory": "/opt/barman/backups",
                "basebackup_retry_sleep": 30,
                "basebackup_retry_times": 3,
                "basebackups_directory": "/opt/barman/backups/bidb/base",
                "check_timeout": 30,
                "compression": "bzip2",
                "conninfo": "host=bidb.xxx.xx port=5445 user=BI password=*REDACTED* dbname=ASBI1",
                "create_slot": "manual",
                "custom_compression_filter": null,
                "custom_compression_magic": null,
                "custom_decompression_filter": null,
                "description": "BI Production PostgreSQL Database",
                "disabled": false,
                "errors_directory": "/opt/barman/backups/bidb/errors",
                "forward_config_path": false,
                "immediate_checkpoint": true,
                "incoming_wals_directory": "/opt/barman/backups/bidb/incoming",
                "last_backup_maximum_age": null,
                "last_backup_minimum_size": null,
                "last_wal_maximum_age": null,
                "max_incoming_wals_queue": null,
                "minimum_redundancy": 0,
                "msg_list": [],
                "name": "bidb",
                "network_compression": false,
                "parallel_jobs": 1,
                "path_prefix": null,
                "post_archive_retry_script": null,
                "post_archive_script": null,
                "post_backup_retry_script": null,
                "post_backup_script": "/opt/barman/bin/backup_check.sh",
                "post_delete_retry_script": null,
                "post_delete_script": null,
                "post_recovery_retry_script": null,
                "post_recovery_script": null,
                "post_wal_delete_retry_script": null,
                "post_wal_delete_script": null,
                "pre_archive_retry_script": null,
                "pre_archive_script": null,
                "pre_backup_retry_script": null,
                "pre_backup_script": "/opt/barman/bin/backup_check.sh",
                "pre_delete_retry_script": null,
                "pre_delete_script": null,
                "pre_recovery_retry_script": null,
                "pre_recovery_script": null,
                "pre_wal_delete_retry_script": null,
                "pre_wal_delete_script": null,
                "primary_ssh_command": null,
                "recovery_options": "",
                "retention_policy": "redundancy 1 b",
                "retention_policy_mode": "auto",
                "reuse_backup": "link",
                "slot_name": null,
                "ssh_command": "ssh enterp...@bidb.xxx.xx",
                "streaming_archiver": false,
                "streaming_archiver_batch_size": 0,
                "streaming_archiver_name": "barman_receive_wal",
                "streaming_backup_name": "barman_streaming_backup",
                "streaming_conninfo": "host=bidb.xxx.xx port=5445 user=BI password=*REDACTED* dbname=ASBI1",
                "streaming_wals_directory": "/opt/barman/backups/bidb/streaming",
                "tablespace_bandwidth_limit": null,
                "wal_retention_policy": "simple-wal 1 b",
                "wals_directory": "/opt/barman/backups/bidb/wals"
            },
            "status": {
                "archive_command": "/usr/bin/rsync -a %p bar...@barman02.xxx.xx:/opt/barman/backups/bidb/incoming/%f",
                "archive_mode": "on",
                "archive_timeout": 0,
                "archived_count": 6311,
                "checkpoint_timeout": 1200,
                "config_file": "/opt/pgsql/9.6/data/postgresql.conf",
                "current_archived_wals_per_second": 0.0736564302833114,
                "current_lsn": "A610/FC9DB0B0",
                "current_size": 5882648667004.0,
                "current_xlog": "000000010000A610000000FC",
                "data_checksums": "off",
                "data_directory": "/opt/pgsql/9.6/data",
                "failed_count": 0,
                "has_backup_privileges": true,
                "hba_file": "/opt/pgsql/9.6/data/pg_hba.conf",
                "hot_standby": "on",
                "ident_file": "/opt/pgsql/9.6/data/pg_ident.conf",
                "included_files": [
                    "/opt/pgsql/9.6/data/postgresql.auto.conf",
                    "/opt/pgsql/9.6/data/postgresql-backend_params.conf",
                    "/opt/pgsql/9.6/data/postgresql-ssl_params.conf"
                ],
                "is_archiving": true,
                "is_in_recovery": false,
                "is_superuser": true,
                "last_archived_time": "Fri Mar  4 08:30:41 2022",
                "last_archived_wal": "000000010000A610000000FB",
                "last_failed_time": null,
                "last_failed_wal": null,
                "max_replication_slots": "3",
                "max_wal_senders": "5",
                "pgespresso_installed": false,
                "postgres_systemid": "6489016419990633760",
                "replication_slot": null,
                "replication_slot_support": true,
                "server_txt_version": "9.6.22",
                "stats_reset": "Thu Mar  3 08:43:35 2022",
                "synchronous_standby_names": [
                    ""
                ],
                "wal_compression": "off",
                "wal_keep_segments": "12",
                "wal_level": "replica",
                "xlog_segment_size": 16777216
            },
            "system_info": {
                "kernel_ver": "Linux bidb.xxx.xx 3.10.0-1160.49.1.el7.x86_64 #1 SMP Tue Nov 30 15:51:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux",
                "python_ver": "",
                "release": "RedHat Linux CentOS Linux release 7.9.2009 (Core)",
                "rsync_ver": "rsync  version 3.1.2  protocol version 31",
                "ssh_ver": ""
            },
            "wals": {
                "last_archived_wal_per_timeline": {
                    "00000001": {
                        "compression": "bzip2",
                        "name": "000000010000A610000000FB",
                        "size": 4093211,
                        "time": 1646379040.493115
                    }
                }
            }
        },
       
                    }
                }
            }
        }
    }
}

Client:
[root@bidb xxxxxxxxxx]# rpm -qa |grep barman
No packages
The barman diagnose command has minor modifications for confidentiality.

Thank you all for your help. I'm learning a lot and I like this group more and more every day. I hope that soon I can help and contribute my little knowledge.

Michael Wallace

unread,
Mar 5, 2022, 2:09:45 AMMar 5
to pgba...@googlegroups.com
Hi Jose,

It's puzzling that the connection to PostgreSQL fails during the backup but succeeds during the `barman check` command. I would start by looking at the PostgreSQL server logs and the Barman server logs during the `barman check` command and then comparing them to the same during the `barman backup` command - are there any signs of the connection failing during the check and needing to be re-established?

Is the connection consistently failing at the same time during the backup?

Best,

Mike

--
--
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+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.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pgbarman/7c025ac7-a8df-41ab-9b13-cd4ff5393a34n%40googlegroups.com.

Jose Manuel Valseca Echevarria

unread,
Mar 7, 2022, 3:51:55 AMMar 7
to pgba...@googlegroups.com
I have the following message in the log:

2022-03-06 23:41:16,733 [109520] barman.backup_executor INFO: This is the first backup for server bidb
2022-03-06 23:41:16,750 [109520] barman.backup_executor INFO: 000000010000A63C0000009F from server bidb has been removed
2022-03-06 23:41:16,751 [109520] barman.backup_executor INFO: Asking PostgreSQL server to finalize the backup.
2022-03-06 23:41:16,777 [109520] barman.backup ERROR: Backup failed issuing start backup command.
2022-03-06 23:41:16,873 [109520] barman.hooks WARNING: /opt/barman/bin/backup_check.sh returned 1
2022-03-06 23:41:16,919 [109520] barman.wal_archiver INFO: No xlog segments found from file archival for bidb.
where can i find more information?

Thank you



--

Jose Manuel Valseca                            

 Asset & Recovery

 EUIGS - Admiral Group

#LeadingTheFuture #BusinessLover

Awesome Job? 

Luca Ferrari

unread,
Mar 7, 2022, 4:46:07 AMMar 7
to Barman, Backup and Recovery Manager for PostgreSQL
On Mon, Mar 7, 2022 at 9:51 AM Jose Manuel Valseca Echevarria
<josemanue...@euigs.com> wrote:
> 2022-03-06 23:41:16,777 [109520] barman.backup ERROR: Backup failed issuing start backup command.

Anything in the PostgreSQL logs that can explain what if failng? Could
it be a permission issue?
Can you try to connect via psql to PostgreSQL and issue, as barman
user, pg_start_backup() and see if there is some hint about the
problem?

Luca

Luca

Jose Manuel Valseca Echevarria

unread,
Mar 7, 2022, 4:48:57 AMMar 7
to pgba...@googlegroups.com
I have launched a new backup with "barman --log-level DEBUG backup bidb" to see if it gives us more clues.

thanks

--
--
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+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.

Jose Manuel Valseca Echevarria

unread,
Mar 8, 2022, 2:05:46 AMMar 8
to pgba...@googlegroups.com
Here is the end of the copy using the debug option

2022-03-08 03:47:10,778 [56790] barman.command_wrappers DEBUG: Command: ['/bin/rsync', '-e', "ssh 'usu...@bidb.xxx.xx' '-o' 'BatchMode=yes' '-o' 'StrictHostKeyChecking=no'", '--exclude=/pg_log/*', '--exclude=/log/*', '--exclude=/pg_xlog/*', '--exclude=/pg_wal/*', '--exclude=/global/pg_control', '--exclude=pgsql_tmp*', '--exclude=postgresql.auto.conf.tmp', '--exclude=current_logfiles.tmp', '--exclude=pg_internal.init', '--exclude=postmaster.pid', '--exclude=postmaster.opts', '--exclude=recovery.conf', '--exclude=standby.signal', '--exclude=pg_dynshmem/*', '--exclude=pg_notify/*', '--exclude=pg_replslot/*', '--exclude=pg_serial/*', '--exclude=pg_stat_tmp/*', '--exclude=pg_snapshots/*', '--exclude=pg_subtrans/*', '--exclude=/pg_tblspc/16421', '--filter=P_/pg_tblspc/16421', '--exclude=/pg_tblspc/16422', '--filter=P_/pg_tblspc/16422', '--exclude=/pg_tblspc/16423', '--filter=P_/pg_tblspc/16423', '--exclude=/pg_tblspc/16424', '--filter=P_/pg_tblspc/16424', '--exclude=/pg_tblspc/16425', '--filter=P_/pg_tblspc/16425', '--exclude=/pg_tblspc/16426', '--filter=P_/pg_tblspc/16426', '--exclude=/pg_tblspc/16427', '--filter=P_/pg_tblspc/16427', '--exclude=/pg_tblspc/16428', '--filter=P_/pg_tblspc/16428', '--exclude=/pg_tblspc/16429', '--filter=P_/pg_tblspc/16429', '--exclude=/pg_tblspc/16430', '--filter=P_/pg_tblspc/16430', '--exclude=/pg_tblspc/16431', '--filter=P_/pg_tblspc/16431', '--exclude=/pg_tblspc/97847091', '--filter=P_/pg_tblspc/97847091', '--exclude=/pg_tblspc/97847170', '--filter=P_/pg_tblspc/97847170', '--exclude=/pg_tblspc/110306038', '--filter=P_/pg_tblspc/110306038', '--exclude=/pg_tblspc/110306039', '--filter=P_/pg_tblspc/110306039', '--exclude=/pg_tblspc/453607245', '--filter=P_/pg_tblspc/453607245', '--exclude=/pg_tblspc/453607246', '--filter=P_/pg_tblspc/453607246', '-rLKpts', '--delete-excluded', '--inplace', '--ignore-missing-args', '--itemize-changes', '--itemize-changes', ' :/opt/pgsql/9.6/data/', '/opt/barman/backups/bidb/base/20220307T100600/data', '--files-from=/tmp/barman-sqEjBI/pgdata_check_56790.list', '--checksum']
2022-03-08 03:47:11,358 [56790] barman.command_wrappers DEBUG: Command return code: 0
2022-03-08 03:47:11,359 [56790] barman.command_wrappers DEBUG: Command stdout:
2022-03-08 03:47:11,359 [56790] barman.command_wrappers DEBUG: Command stderr:
2022-03-08 03:47:11,359 [56790] barman.copy_controller INFO: Copy step 72 of 73: [bucket 0] finished (duration: less than one second) copy files with checksum from remote PGDATA directory: /opt/pgsql/9.6/data/
2022-03-08 03:47:11,367 [56790] barman.copy_controller INFO: Copy step 73 of 73: [global] starting copy remote pg_control file: /opt/pgsql/9.6/data/global/pg_control
2022-03-08 03:47:11,368 [56790] barman.command_wrappers DEBUG: Command: ['/bin/rsync', '-e', "ssh 'usu...@bidb.xxx.xx' '-o' 'BatchMode=yes' '-o' 'StrictHostKeyChecking=no'", '-rLKpts', '--delete-excluded', '--inplace', '--ignore-missing-args', '--itemize-changes', '--itemize-changes', ' :/opt/pgsql/9.6/data/global/pg_control', '/opt/barman/backups/bidb/base/20220307T100600/data/global/pg_control']
2022-03-08 03:47:11,889 [56790] barman.command_wrappers DEBUG: Command return code: 0
2022-03-08 03:47:11,889 [56790] barman.command_wrappers DEBUG: Command stdout: >f+++++++++ pg_control
2022-03-08 03:47:11,890 [56790] barman.command_wrappers DEBUG: Command stderr:
2022-03-08 03:47:11,890 [56790] barman.copy_controller INFO: Copy step 73 of 73: [global] finished (duration: less than one second) copy remote pg_control file: /opt/pgsql/9.6/data/global/pg_control
2022-03-08 03:47:11,893 [56432] barman.copy_controller INFO: Copy finished (safe before None)
2022-03-08 03:47:12,002 [56432] barman.backup_executor INFO: Copy done (time: 17 hours, 40 minutes, 35 seconds)
2022-03-08 03:47:12,024 [56432] barman.backup_executor INFO: This is the first backup for server bidb
2022-03-08 03:47:12,161 [56432] barman.backup_executor INFO:    000000010000A64D000000C7 from server bidb has been removed
2022-03-08 03:47:12,162 [56432] barman.backup_executor INFO:    000000010000A64D000000C8 from server bidb has been removed
2022-03-08 03:47:12,164 [56432] barman.backup_executor INFO:    000000010000A64D000000C9 from server bidb has been removed
2022-03-08 03:47:12,164 [56432] barman.backup_executor INFO:    000000010000A64D000000CA from server bidb has been removed
2022-03-08 03:47:12,165 [56432] barman.backup_executor INFO: Asking PostgreSQL server to finalize the backup.
2022-03-08 03:47:12,180 [56432] barman.backup ERROR: Backup failed issuing start backup command.
2022-03-08 03:47:12,191 [56432] barman.hooks DEBUG: Attempt to run backup_script: /opt/barman/bin/backup_check.sh
2022-03-08 03:47:12,191 [56432] barman.command_wrappers DEBUG: Command: '/opt/barman/bin/backup_check.sh'
2022-03-08 03:47:12,284 [56432] barman.command_wrappers DEBUG: Command return code: 1
2022-03-08 03:47:12,284 [56432] barman.command_wrappers DEBUG: Command stdout:
2022-03-08 03:47:12,284 [56432] barman.command_wrappers DEBUG: Command stderr:
2022-03-08 03:47:12,285 [56432] barman.hooks WARNING: /opt/barman/bin/backup_check.sh returned 1
2022-03-08 03:47:12,286 [56432] barman.server DEBUG: Starting archive-wal for server bidb
2022-03-08 03:47:12,287 [56432] barman.wal_archiver INFO: No xlog segments found from file archival for bidb.
2022-03-08 03:48:01,891 [36479] barman.cli INFO: Skipping inactive server 'eprogesdocdb01'
2022-03-08 03:48:01,896 [36479] barman.backup_executor WARNING: No backup strategy set for server 'eprogesdocdb02' (using default 'exclusive_backup').
2022-03-08 03:48:01,896 [36479] barman.backup_executor WARNING: The default backup strategy will change to 'concurrent_backup' in the future. Explicitly set 'backup_options' to silence this warning.
2022-03-08 03:48:02,288 [36485] barman.wal_archiver INFO: No xlog segments found from file archival for xprojobs03.
2022-03-08 03:48:02,352 [36483] barman.wal_archiver INFO: Found 23 xlog segments from file archival for bidb. Archive all segments in one run.
2022-03-08 03:48:02,352 [36483] barman.wal_archiver INFO: Archiving segment 1 of 23 from file archival: bidb/000000010000A65D000000A4
2022-03-08 03:48:02,354 [36484] barman.backup_executor WARNING: No backup strategy set for server 'eprogesdocdb02' (using default 'exclusive_backup').
2022-03-08 03:48:02,354 [36484] barman.backup_executor WARNING: The default backup strategy will change to 'concurrent_backup' in the future. Explicitly set 'backup_options' to silence this warning.
2022-03-08 03:48:02,356 [36484] barman.wal_archiver INFO: No xlog segments found from file archival for Alfresco.
2022-03-08 03:48:04,496 [36483] barman.wal_archiver INFO: Archiving segment 2 of 23 from file archival: bidb/000000010000A65D000000A5
2022-03-08 03:48:06,669 [36483] barman.wal_archiver INFO: Archiving segment 3 of 23 from file archival: bidb/000000010000A65D000000A6
2022-03-08 03:48:08,945 [36483] barman.wal_archiver INFO: Archiving segment 4 of 23 from file archival: bidb/000000010000A65D000000A7
2022-03-08 03:48:11,299 [36483] barman.wal_archiver INFO: Archiving segment 5 of 23 from file archival: bidb/000000010000A65D000000A8
2022-03-08 03:48:13,583 [36483] barman.wal_archiver INFO: Archiving segment 6 of 23 from file archival: bidb/000000010000A65D000000A9

I have no idea what is going on as the network traffic is not cut off at any time.

Jose Manuel Valseca Echevarria

unread,
Mar 10, 2022, 4:03:11 AMMar 10
to Barman, Backup and Recovery Manager for PostgreSQL
Is it possible to re-establish the communication if it has been momentarily lost or continue with the copy if it has failed, or is it necessary to launch a new one?

I can't manage to make a complete copy

thanks

Luca Ferrari

unread,
Mar 10, 2022, 4:18:54 AMMar 10
to Barman, Backup and Recovery Manager for PostgreSQL
On Thu, Mar 10, 2022 at 10:03 AM Jose Manuel Valseca Echevarria
<josemanue...@euigs.com> wrote:
>
> Is it possible to re-establish the communication if it has been momentarily lost or continue with the copy if it has failed, or is it necessary to launch a new one?
>

AFAIK no, this is a feature available for example in pgbackrest but
barman will start a backup copy from scratch every time.

Luca

Jose Manuel Valseca Echevarria

unread,
Mar 10, 2022, 4:45:07 AMMar 10
to pgba...@googlegroups.com
This is the error that appears in the log. What do you think could be wrong?
What is the command you are referring to? "barman.backup ERROR: Backup failed issuing start backup command"

Best regards


2022-03-10 03:38:58,772 [13763] barman.backup_executor INFO: This is the first backup for server bidb
2022-03-10 03:38:59,015 [13763] barman.backup_executor INFO: 000000010000A681000000D6 from server bidb has been removed
2022-03-10 03:38:59,016 [13763] barman.backup_executor INFO: Asking PostgreSQL server to finalize the backup.
2022-03-10 03:38:59,028 [13763] barman.backup ERROR: Backup failed issuing start backup command.
2022-03-10 03:38:59,037 [13763] barman.hooks DEBUG: Attempt to run backup_script: /opt/barman/bin/backup_check.sh
2022-03-10 03:38:59,037 [13763] barman.command_wrappers DEBUG: Command: '/opt/barman/bin/backup_check.sh'
2022-03-10 03:38:59,121 [13763] barman.command_wrappers DEBUG: Command return code: 1
2022-03-10 03:38:59,122 [13763] barman.command_wrappers DEBUG: Command stdout:
2022-03-10 03:38:59,122 [13763] barman.command_wrappers DEBUG: Command stderr:
2022-03-10 03:38:59,122 [13763] barman.hooks WARNING: /opt/barman/bin/backup_check.sh returned 1

Regards

--
--
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+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.

Jose Manuel Valseca Echevarria

unread,
Mar 11, 2022, 2:15:50 AMMar 11
to Barman, Backup and Recovery Manager for PostgreSQL

Good morning guys. The Network department has monitored the network during the whole copying process and it is not a network problem.
On the other hand I have the following information from the database:

edb=# \c bidb
Password for user enterprisedb:
You are now connected to database "bidb" as user "enterprisedb".
bidb=# show tcp_keepalives_idle;
tcp_keepalives_idle
---------------------
0
(1 row)
bidb=# show tcp_keepalives_interval;
tcp_keepalives_interval
-------------------------
0
(1 row)
bidb=# show tcp_keepalives_count;
tcp_keepalives_count
----------------------
0
(1 row)
 
Please help me. I don't know what is going on and I have been without copies for 2 weeks.

Best regards and thanks

Jose Manuel Valseca Echevarria

unread,
Mar 14, 2022, 7:40:29 AMMar 14
to Barman, Backup and Recovery Manager for PostgreSQL
This error is the one I get in the log of the database. Sorry for the language but the error is in Spanish.
2022-03-13 07:00:07 GMT:192.168.226.75(36986):xx:BIdb1: LOG: desconexión: duración de sesión: 0:00:01.293 usuario=xx base=xxx host=192.168.xx.xx port=36xxxx 2022-03-13 22:00:11 GMT:192.168.226.75(36978):xx:BIdb: FATAL: terminando la conexión debido a una orden del administrador 2022-03-13 22:00:11 GMT:192.168.226.75(36978):xx:BIdb: WARNING: abortando el backup porque el proceso servidor terminó antes de que pg_stop_backup fuera invocada

thanks

Jose Manuel Valseca Echevarria

unread,
Mar 21, 2022, 4:48:48 AMMar 21
to Barman, Backup and Recovery Manager for PostgreSQL
New information:

This server does not use postgres, it uses edb:

edb-as96-server-core-9.6.22.29-1.rhel7.x86_64
edb-as96-server-indexadvisor-9.6.22.29-1.rhel7.x86_64
edb-as96-server-9.6.22.29-1.rhel7.x86_64
edb-as96-server-sslutils-1.3-1.rhel7.x86_64
edb-as96-server-libs-9.6.22.29-1.rhel7.x86_64
edb-as96-server-contrib-9.6.22.29-1.rhel7.x86_64
edb-as96-server-sqlprotect-9.6.22.29-1.rhel7.x86_64
edb-as96-server-pltcl-9.6.22.29-1.rhel7.x86_64
edb-as96-server-plpython-9.6.22.29-1.rhel7.x86_64
edb-as96-server-docs-9.6.22.29-1.rhel7.x86_64
edb-as96-server-sqlprofiler-4.0-1.rhel7.x86_64
edb-repo-20-2.noarch
libicu-edb-53.1-11.rhel7.x86_64
edb-as96-server-pldebugger-1.1-1.rhel7.x86_64
edb-as96-server-client-9.6.22.29-1.rhel7.x86_64
edb-as96-server-plperl-9.6.22.29-1.rhel7.x86_64
edb-as96-server-devel-9.6.22.29-1.rhel7.x86_64


I still can't find a solution :(

Luca Ferrari

unread,
Mar 21, 2022, 5:33:04 AMMar 21
to Barman, Backup and Recovery Manager for PostgreSQL
On Thu, Mar 10, 2022 at 10:45 AM Jose Manuel Valseca Echevarria
<josemanue...@euigs.com> wrote:
> 2022-03-10 03:38:59,028 [13763] barman.backup ERROR: Backup failed issuing start backup command.

This meks me think that you could be using the exclusive backlup
instead of the concurrent one, could it be a start backup is still in
progress?
But I don't know how to check without issuing manually a
pg_stop_backup and start over a new backup.


> 2022-03-10 03:38:59,037 [13763] barman.command_wrappers DEBUG: Command: '/opt/barman/bin/backup_check.sh'
> 2022-03-10 03:38:59,121 [13763] barman.command_wrappers DEBUG: Command return code: 1

This is something custom, right? Any chance this is keeping the backup to fail?

Luca

Jose Manuel Valseca Echevarria

unread,
Mar 21, 2022, 6:10:48 AMMar 21
to pgba...@googlegroups.com
These scripts are to notify the final status of the copy. If you need it, I can put a copy here.
Could you tell me how to do the pg_stop_backup by hand, what steps do you want me to do to recreate the error?

Best regards

--
--
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+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.

Luca Ferrari

unread,
Mar 22, 2022, 3:58:20 AMMar 22
to Barman, Backup and Recovery Manager for PostgreSQL
On Mon, Mar 21, 2022 at 11:10 AM Jose Manuel Valseca Echevarria
<josemanue...@euigs.com> wrote:
>
> These scripts are to notify the final status of the copy. If you need it, I can put a copy here.
> Could you tell me how to do the pg_stop_backup by hand, what steps do you want me to do to recreate the error?


I would connect to postgresql and execute a pg_stop_backup, something like:
psql -U postgres -c 'SELECT pg_stop_backup();'
and see if it complains about no backup in progress, then start over a
new backup and see what happens.

Luca

Jose Manuel Valseca Echevarria

unread,
Mar 22, 2022, 5:14:21 AMMar 22
to pgba...@googlegroups.com
I get the same result
edb=# SELECT pg_stop_backup();'
ERROR: no hay un respaldo exclusivo en curso

--
--
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+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.

Luca Ferrari

unread,
Mar 22, 2022, 6:05:26 AMMar 22
to Barman, Backup and Recovery Manager for PostgreSQL
On Tue, Mar 22, 2022 at 10:14 AM Jose Manuel Valseca Echevarria
<josemanue...@euigs.com> wrote:
>
> I get the same result
> edb=# SELECT pg_stop_backup();'
> ERROR: no hay un respaldo exclusivo en curso

This means there is no backup in progress, then barman should work. If
not, I've at the moment no particular idea.

Luca
Reply all
Reply to author
Forward
0 new messages