Обсуждение: archiving transaction log file failed too many times, will try again later
Hello, I'm running a barman test system. Last night there was a Hardware failure. my postgres.conf looks like root@srv-007:/var/log/postgresql# cat /etc/postgresql/9.3/barman_recover/postgresql.conf | egrep -v "(^#|^$|^;)" data_directory = '/var/lib/postgresql/9.3/barman_recover' # use data in another directory listen_addresses = '*' port = 5437 max_connections = 100 wal_level = archive archive_mode = on archive_command = false log_line_prefix = '%t ' log_timezone = 'localtime' datestyle = 'iso, mdy' timezone = 'localtime' lc_messages = 'en_US.iso885915' # locale for system error message lc_monetary = 'en_US.iso885915' # locale for monetary formatting lc_numeric = 'en_US.iso885915' # locale for number formatting lc_time = 'en_US.iso885915' # locale for time formatting default_text_search_config = 'pg_catalog.english' root@srv-007:/var/log/postgresql# and the logfile .../postgresql-9.3-barman_recover.log is full of 2014-05-23 10:58:56 CEST LOG: archive command failed with exit code 1 2014-05-23 10:58:56 CEST DETAIL: The failed archive command was: false 2014-05-23 10:58:57 CEST LOG: archive command failed with exit code 1 2014-05-23 10:58:57 CEST DETAIL: The failed archive command was: false 2014-05-23 10:58:58 CEST LOG: archive command failed with exit code 1 2014-05-23 10:58:58 CEST DETAIL: The failed archive command was: false 2014-05-23 10:58:58 CEST WARNING: archiving transaction log file "00000001000000000000000C" failed too many times, will try again later How can I fix this? Thanks, Basti
Re: archiving transaction log file failed too many times, will try again later
От
Jerry Sievers
Дата:
basti <mailinglist@unix-solution.de> writes: > Hello, > I'm running a barman test system. > Last night there was a Hardware failure. > my postgres.conf looks like > > root@srv-007:/var/log/postgresql# cat > /etc/postgresql/9.3/barman_recover/postgresql.conf | egrep -v "(^#|^$|^;)" > data_directory = '/var/lib/postgresql/9.3/barman_recover' # use data in > another directory > listen_addresses = '*' > port = 5437 > max_connections = 100 > wal_level = archive > archive_mode = on > archive_command = false False?... You are forcing your archiving to fail and thus be queued for later shipment. > log_line_prefix = '%t ' > log_timezone = 'localtime' > datestyle = 'iso, mdy' > timezone = 'localtime' > lc_messages = 'en_US.iso885915' # locale for system error message > lc_monetary = 'en_US.iso885915' # locale for monetary formatting > lc_numeric = 'en_US.iso885915' # locale for number formatting > lc_time = 'en_US.iso885915' # locale for time formatting > default_text_search_config = 'pg_catalog.english' > root@srv-007:/var/log/postgresql# > > and the logfile .../postgresql-9.3-barman_recover.log is full of > 2014-05-23 10:58:56 CEST LOG: archive command failed with exit code 1 > 2014-05-23 10:58:56 CEST DETAIL: The failed archive command was: false > 2014-05-23 10:58:57 CEST LOG: archive command failed with exit code 1 > 2014-05-23 10:58:57 CEST DETAIL: The failed archive command was: false > 2014-05-23 10:58:58 CEST LOG: archive command failed with exit code 1 > 2014-05-23 10:58:58 CEST DETAIL: The failed archive command was: false > 2014-05-23 10:58:58 CEST WARNING: archiving transaction log file > "00000001000000000000000C" failed too many times, will try again later > > How can I fix this? > > Thanks, > Basti -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800