Re: WAL Archiving Stopped

[Filip RembiaÅkowski <plk.zuber@xxxxxxxxx>]

W dniu 4 stycznia 2011 14:55 uÅytkownik Norberto Delle <betodelle@xxxxxxxxx> napisaÅ:

Em 3/1/2011 18:39, Filip RembiaÅkowski escreveu:

archiver process will retry later; it never stops trying, sleep time
is just longer.

2011/1/3, Norberto Delle<betodelle@xxxxxxxxx>:

Hi all

I have a PostgreSQL 9.0.1 instance, with WAL Archiving.
Today, after some failed tries to archive a WAL file, it stopped trying
to archive the files,
but the number of logfiles in the pg_xlog directory keep growing.
Any ideas of what is going on?

Norberto


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Hi Filip

It was taking too long to retry, Âa matter of hours.
I had to restart the service to it start trying to archive the wal files.

that's strange; from the source code I would think that it will retry indefinitely.
( http://doxygen.postgresql.org/pgarch_8c-source.html )

I have also tested this with archive_command = "/bin/false" and it works as expected.
archiver does 3 retries, then sleep for 60 seconds hardcoded timeout.


2011-01-04 18:11:41.407 CET [2375]ÂÂÂ WARNING:Â transaction log file "000000010000000000000008" could not be archived: too many failures
2011-01-04 18:12:41.474 CET [2375]ÂÂÂ LOG:Â archive command failed with exit code 1
2011-01-04 18:12:41.474 CET [2375]ÂÂÂ DETAIL:Â The failed archive command was: /bin/false
2011-01-04 18:12:42.478 CET [2375]ÂÂÂ LOG:Â archive command failed with exit code 1
2011-01-04 18:12:42.478 CET [2375]ÂÂÂ DETAIL:Â The failed archive command was: /bin/false
2011-01-04 18:12:43.484 CET [2375]ÂÂÂ LOG:Â archive command failed with exit code 1
2011-01-04 18:12:43.484 CET [2375]ÂÂÂ DETAIL:Â The failed archive command was: /bin/false
2011-01-04 18:12:43.484 CET [2375]ÂÂÂ WARNING:Â transaction log file "000000010000000000000008" could not be archived: too many failures

(and so on...)



Â

Norberto