Thread: WARNING: transaction log file "....." could not be archived: too many failures

Hello.

The following message appears continuously in the log file of postgresql :

Jan 28 11:35:01 abcd postgres[28359]: [81-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:01 abcd postgres[28359]: [81-2]  code 256
Jan 28 11:35:02 abcd postgres[28359]: [82-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:02 abcd postgres[28359]: [82-2]  code 256
Jan 28 11:35:03 abcd postgres[28359]: [83-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:03 abcd postgres[28359]: [83-2]  code 256
Jan 28 11:35:03 abcd postgres[28359]: [84-1] WARNING:  transaction log file "000000010000000000000085" could not be archived: too many failures


The problem is that the requested file is not available anymore. How can I tell postgres to bypass this file ?

Thanks
Joby

Joby Joba <jobyjoba59@gmail.com> wrote:

> Jan 28 11:35:01 abcd postgres[28359]: [81-1] LOG:  archive command
> "cp "pg_xlog/000000010000000000000085"
> /u10/postgres/archive/"000000010000000000000085"" failed: return
> Jan 28 11:35:01 abcd postgres[28359]: [81-2]  code 256

> The problem is that the requested file is not available anymore.
> How can I tell postgres to bypass this file ?

Get a new base backup and start the recovery over.  Be sure to fix
whatever broken process caused the WAL file to be discarded while it
might still be needed.

-Kevin