Barman not connecting to Postgres
Salman Khan
Server main:
PostgreSQL: FAILED
directories: OK
retention policy settings: OK
backup maximum age: OK (no last_backup_maximum_age provided)
compression settings: OK
minimum redundancy requirements: FAILED (have 0 backups, expected at least 1)
ssh: OK (PostgreSQL server)
not in recovery: OK
Barman logs:
2017-04-18 15:50:58,042 [27303] barman.cli DEBUG: Initialised Barman version 1.5.1 (config: /etc/barman.conf, args: {'command': 'check', 'server_name': ['main'], 'format': 'console', 'debug': False, 'quiet': False, 'nagios': False})
2017-04-18 15:50:58,051 [27303] barman.server DEBUG: Error retrieving PostgreSQL setting 'data_directory': must be superuser to examine "data_directory"
2017-04-18 15:50:58,052 [27303] barman.server DEBUG: Error retrieving PostgreSQL setting 'wal_level': current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,052 [27303] barman.server DEBUG: Error retrieving PostgreSQL version: current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,053 [27303] barman.server DEBUG: Error retrieving pgespresso information: current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,054 [27303] barman.server DEBUG: Error calling pg_is_in_recovery() function: current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,054 [27303] barman.server DEBUG: Error retrieving current xlog: current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,055 [27303] barman.server DEBUG: Error retrieving PostgreSQL configuration files location: current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,056 [27303] barman.server DEBUG: Error retrieving PostgreSQL setting 'data_directory': current transaction is aborted, commands ignored until end of transaction block
2017-04-18 15:50:58,056 [27303] barman.server ERROR: Check 'PostgreSQL' failed for server 'main'
2017-04-18 15:50:58,057 [27303] barman.server DEBUG: Check 'directories' succeeded for server 'main'
2017-04-18 15:50:58,057 [27303] barman.server DEBUG: Check 'retention policy settings' succeeded for server 'main'
2017-04-18 15:50:58,057 [27303] barman.server DEBUG: Check 'backup maximum age' succeeded for server 'main'
2017-04-18 15:50:58,057 [27303] barman.server DEBUG: Check 'compression settings' succeeded for server 'main'
2017-04-18 15:50:58,058 [27303] barman.server ERROR: Check 'minimum redundancy requirements' failed for server 'main'
2017-04-18 15:50:58,058 [27303] barman.command_wrappers DEBUG: Command: ['ssh', 'post...@127.0.0.1', '-o', 'BatchMode=yes', '-o', 'StrictHostKeyChecking=no', 'true']
2017-04-18 15:50:58,174 [27303] barman.command_wrappers DEBUG: Command return code: 0
2017-04-18 15:50:58,174 [27303] barman.command_wrappers DEBUG: Command stdout:
2017-04-18 15:50:58,175 [27303] barman.command_wrappers DEBUG: Command stderr:
2017-04-18 15:50:58,175 [27303] barman.server DEBUG: Check 'ssh' succeeded for server 'main'
2017-04-18 15:50:58,181 [27303] barman.server DEBUG: Check 'not in recovery' succeeded for server 'main'
Diagnose Output:
{
"global": {
"config": {
"barman_home": "/home/barman",
"barman_user": "barman",
"errors_list": [],
"log_file": "/home/barman/barman.log",
"log_level": "DEBUG"
},
"system_info": {
"barman_ver": "1.5.1",
"kernel_ver": "Linux A0310SAPIGWEdgeAx01.bss.telenor.com.pk 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux",
"python_ver": "Python 2.6.6",
"release": "RedHat Linux Red Hat Enterprise Linux Server release 6.5 (Santiago)",
"rsync_ver": "rsync version 3.0.6 protocol version 30",
"ssh_ver": "OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010"
}
},
"servers": {
"main": {
"backups": {},
"config": {
"active": true,
"backup_directory": "/home/barman/main",
"backup_options": "exclusive_backup",
"bandwidth_limit": null,
"barman_home": "/home/barman",
"barman_lock_directory": "/home/barman",
"basebackup_retry_sleep": 30,
"basebackup_retry_times": 0,
"basebackups_directory": "/home/barman/main/base",
"compression": null,
"conninfo": "host=127.0.0.1 user=postgres password=postgres dbname=postgres port=5432",
"copy_method": "rsync",
"custom_compression_filter": null,
"custom_decompression_filter": null,
"description": null,
"disabled": false,
"immediate_checkpoint": false,
"incoming_wals_directory": "/home/barman/main/incoming",
"last_backup_maximum_age": null,
"minimum_redundancy": 1,
"msg_list": [],
"name": "main",
"network_compression": false,
"post_archive_retry_script": null,
"post_archive_script": null,
"post_backup_retry_script": null,
"post_backup_script": null,
"pre_archive_retry_script": null,
"pre_archive_script": null,
"pre_backup_retry_script": null,
"pre_backup_script": null,
"recovery_options": "",
"retention_policy": null,
"retention_policy_mode": "auto",
"reuse_backup": null,
"ssh_command": "ssh post...@127.0.0.1",
"tablespace_bandwidth_limit": null,
"wal_retention_policy": "main",
"wals_directory": "/home/barman/main/wals"
},
"status": {
"archive_command": "(disabled)",
"archive_mode": "off",
"current_xlog": null,
"data_directory": null,
"last_archived_wal": null,
"pgespresso_installed": false,
"server_txt_version": null,
"wal_level": null
},
"system_info": {
"kernel_ver": "Linux A0310SAPIGWEdgeAx01.bss.telenor.com.pk 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux",
"python_ver": "Python 2.6.6",
"release": "RedHat Linux Red Hat Enterprise Linux Server release 6.5 (Santiago)",
"rsync_ver": "rsync version 3.0.6 protocol version 30",
"ssh_ver": "OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010"
}
}
}
}
Any help on this would be much appreciated.
Regards,
Salman
Salman Khan
--
--
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 a topic in the Google Groups "Barman, Backup and Recovery Manager for PostgreSQL" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pgbarman/DObNH4Qh5jc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pgbarman+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Gabriele Bartolini
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 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.
Salman Khan
Hi Salman,the archive_command you are using is completely wrong. While Barman is there to help configuring PostgreSQL Disaster recovery, that does not prevent you from knowing the basics and fundamentals of PITR in PostgreSQL.Also, we are putting a lot of efforts in the documentation and I think that is pretty clear in explaining what needs to be done and all the steps you have to follow.Obviously it is not, as I imagine you have read it thoroughly. According to you, is there anything you think it should be improved in the documentation? If so, please feel free to send a pull request as even the documentation is open source.Thanks,GabrieleP.S.: By the way, backing up locally is a massive SPOF. I hope you are aware of that.
--
Gabriele Bartolini - 2ndQuadrant Italia - Director
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it
Salman Khan
Hi,
Thanks for the reply and pointing it out.The efforts you have put in the tool and it's documentation are really appreciated. Keep up the good work.I have a few points that I would like to take up. Have been working on barman for the past week now without a gap. I'll note them down and share.Lastly I am aware of the SPOF but this is the staging environment. I'll use a separate server for production backups.Regards,Salman
Gabriele Bartolini
Gabriele Bartolini - 2ndQuadrant Italia - Director
PostgreSQL Training, Services and Support
Salman Khan
Hi Salman,Can I ask you why you installed Barman 1.5.1 instead of 2.1? Also, have you followed the instructions regarding setting up WAL archiving?Cheers,Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia - Director
PostgreSQL Training, Services and Support
gabriele.bartolini@2ndQuadrant.it | www.2ndQuadrant.it