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

HI

I am getting the following error in my postgresql log file.

cp: cannot stat `pg_xlog/000000010000097600000051': No such file or directory
gzip: /usr/local/pgsql/wal_archive/000000010000097600000051: No such file or directory
<  76800 2012-10-16 07:58:11.903 CDT  00000 >LOG:  archive command failed with exit code 1
<  76800 2012-10-16 07:58:11.903 CDT  00000 >DETAIL:  The failed archive command was: /usr/local/pgsql/data/wal_archive_command.sh pg_xlog/000000010000097600000051 000000010000097600000051
<  76800 2012-10-16 07:58:11.903 CDT  01000 >WARNING:  transaction log file "000000010000097600000051" could not be archived: too many failures


Earlier when the database was started , the directory /usr/local/pgsql/wal_archive/ did not exist..Now I have created this directory,,,But im still getting this error...
Moreover there are around 15000 files in data/pg_xlog/archive_status and all of them have status as .ready..

Can anyone let me know if they have faced this kind of issue before and how do I rectify it?

DISCLAIMER:

Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and delete this e-mail , whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Ver sé Innovation Pvt Ltd.

Mathew Thomas <mathew.thomas@verse.in> writes:
> I am getting the following error in my postgresql log file.

> cp: cannot stat `pg_xlog/000000010000097600000051': No such file or
> directory

If there's a .ready file corresponding to that, remove it.
I'm not entirely sure how you could have ended up with a .ready file
but not the base file, but that seems the only explanation of this
symptom.

            regards, tom lane

Thanks...Removing the .ready files worked...

Mathew

DISCLAIMER:

Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and delete this e-mail , whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Ver sé Innovation Pvt Ltd.