My postgres 9.6 master database is trying to archive a WAL file that0000000300005770000000EB
does not exist anymore. In the log I find lots of this error:
< 2018-09-27 22:25:23.027 CEST >WARNING: archiving transaction log
file "0000000300005770000000EB" failed too many times, will try again
later < 2018-09-27 22:25:23.215 CEST >LOG: archive command failed
with exit code 23 < 2018-09-27 22:25:23.215 CEST >DETAIL: The
failed archive command was: rsync -a pg_xlog/0000000300005770000000EB email@example.com:/mnt/nfs/barman/datavarehus/incoming/
(I am running streaming replication and also barman, this is happening
on my master).
Archive parameters in postgresql.conf
[postgres@datavarehus: ~]$ grep ^arch 9.6/data/postgresql.conf
archive_mode = on archive_command = 'rsync -a %p firstname.lastname@example.org:/mnt/nfs/barman/datavarehus/incoming/%f'
How can I get out of this?
You must have removed that WAL file from "pg_xlog" before it was archived.
To get rid of this error, you can temporarily set
archive_command = '/bin/true'
Then PostgreSQL will believe that the WAL files are archived correctly,
even though they are not.
Once pg_stat_archiver shows that PostgreSQL has caught up to WAL files
that actually exist, you can restore the original setting.
After that, create a new base backup as soon as possible!
|Location:||Huddersfield, West Yorkshire, UK|
|Nodes:||8 (1 / 7)|