The app is working properly, but not sure what happened for the backup after the move.
Sending notification using Notifier::Mail. These files will be removed at that time! 'Oktob Production Database Backup (oktob_database_backup)' Make sure you check these files before the next scheduled backup for This folder may contain completed Archives and/or Database backups.
Errno::EPERM: Operation not permitted - 'pg_dump' returned exit code: 1 The following system errors were returned: Is the server running on host "172.17.0.1" and accepting pg_dump: connection to database "oktob" failed: could not connect to server: Connection refused (Note: may be interleaved if multiple commands returned error messages) Database::PostgreSQL::Error: Dump Failed! Model::Error: Backup for Oktob Production Database Backup (oktob_database_backup) Failed! The temporary files which had to be removed should not have existed. concerning this backup: 'Oktob Production Database Backup (oktob_database_backup)'
Please check the log for messages and/or your notifications '/root/Backup/.tmp/oktob_database_backup' The temporary packaging folder still exists! The configurations are stored in /etc/environment # DatabaseĮxport AWS_DATABASE_BACKUP_BUCKET_NAME=''Įrror message: 9 11:04:34] Performing Backup for 'Oktob Production Database Backup (oktob_database_backup)'! # See the documentation for other delivery options. # The default delivery method for Mail Notifiers is 'SMTP'. Recently I moved the app from one droplet to another (changed the region) and then the backup is failing to connect to the DB.īackup model ( /root/Backup/models/oktob_database_backup.rb) Model.new(:oktob_database_backup, 'Oktob Production Database Backup') do On my 9.I'm running a Rails app using Dokku on DigitalOcean and using Rails backup gem to regularly take DB backup. Sudo lsof -n -u postgres |grep LISTEN or sudo netstat -ltnp | grep postgres should show the TCP/IP addresses and ports PostgreSQL is listening onīTW, I think you must be on an old version. Ps -f -u postgres should list postgres processes (If you are not connecting on localhost, it may also be a network firewall that's blocking TCP/IP connections, but I'm guessing you're using the defaults since you didn't say). (unlikely) there's an iptables rule blocking loopback connections PostgreSQL is listening on a different port to the one you're connecting on
POSTGRESQL CREATE DATABASE DUMP CONNECTION REFUSED MAC OS X
This seems to be an issue on some older Mac OS X versions that have weird IPv6 socket behaviour, and on some older Windows versions. Lastly, ensure you restart postgres after making these changes. It looks like you are using the wrong configuration parameter name, and might have a space surrounding the asterisk. PostgreSQL is only listening on IPv4 ( 0.0.0.0 or 127.0.0.1) and you're connecting on IPv6 ( ::1) or vice versa. Ensure that the nf file has an entry for listenaddresses''. PostgreSQL isn't listening for TCP/IP connections ( listen_addresses in nf) Assuming you're connecting on localhost port 5432 (the defaults for a standard PostgreSQL install), then either: You haven't shown the command that produces the error. The error you quote has nothing to do with pg_hba.conf it's failing to connect, not failing to authorize the connection.Ĭheck that the hostname and port are correct and that the postmaster is accepting TCP/IP connections
0 kommentar(er)
