Обсуждение: Archive WAL Logs Failed
Hi All,
Yesterday, we'd archiver problems in copying archived wal files from pg_xlog to archive destination at the end of full hotbackup. Below are the errors from server logs.
What makes me to wonder is that why does archiver tries to copy "000000010000000800000074.0066C9C0.backup" again when it's already been archived. As soon I removed "000000010000000800000074.0066C9C0.backup" from archive location, then archiver was happy to copy again and moved on to archiving 000000010000000800000074 etc.
2006-11-07 00:35:23 CST LOG: archived transaction log file "000000010000000800000074.0066C9C0.backup"
2006-11-07 00:35:23 CST LOG: archive command "test ! -f /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup && cp pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" failed: return code 256
Any idea what may be going on here.
Thanks,
Stalin
PG814, RH4.0
You're not by chance doing a filesystem copy into /b01/pgdata/archive/db1? On Tue, Nov 07, 2006 at 10:15:01AM -0800, Subbiah, Stalin wrote: > Hi All, > > Yesterday, we'd archiver problems in copying archived wal files from > pg_xlog to archive destination at the end of full hotbackup. Below are > the errors from server logs. > What makes me to wonder is that why does archiver tries to copy > "000000010000000800000074.0066C9C0.backup" again when it's already been > archived. As soon I removed "000000010000000800000074.0066C9C0.backup" > from archive location, then archiver was happy to copy again and moved > on to archiving 000000010000000800000074 etc. > > 2006-11-07 00:35:23 CST LOG: archived transaction log file > "000000010000000800000074.0066C9C0.backup" > 2006-11-07 00:35:23 CST LOG: archive command "test ! -f > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup && cp > pg_xlog/000000010000000800000074.0066C9C0.backup > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" > failed: return code 256 > > Any idea what may be going on here. > > Thanks, > Stalin > > PG814, RH4.0 > > > -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
Nope. Only archiver does that. Since we had this problem the backups are running just fine and no problems whatsoever with archiver either. Strange!!! -----Original Message----- From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Jim C. Nasby Sent: Tuesday, November 07, 2006 10:26 PM To: Subbiah, Stalin Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] Archive WAL Logs Failed You're not by chance doing a filesystem copy into /b01/pgdata/archive/db1? On Tue, Nov 07, 2006 at 10:15:01AM -0800, Subbiah, Stalin wrote: > Hi All, > > Yesterday, we'd archiver problems in copying archived wal files from > pg_xlog to archive destination at the end of full hotbackup. Below are > the errors from server logs. > What makes me to wonder is that why does archiver tries to copy > "000000010000000800000074.0066C9C0.backup" again when it's already > been archived. As soon I removed "000000010000000800000074.0066C9C0.backup" > from archive location, then archiver was happy to copy again and moved > on to archiving 000000010000000800000074 etc. > > 2006-11-07 00:35:23 CST LOG: archived transaction log file > "000000010000000800000074.0066C9C0.backup" > 2006-11-07 00:35:23 CST LOG: archive command "test ! -f > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup && cp > pg_xlog/000000010000000800000074.0066C9C0.backup > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" > failed: return code 256 > > Any idea what may be going on here. > > Thanks, > Stalin > > PG814, RH4.0 > > > -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
On Tue, 2006-11-07 at 10:15 -0800, Subbiah, Stalin wrote: > Yesterday, we'd archiver problems in copying archived wal files from > pg_xlog to archive destination at the end of full hotbackup. Below are > the errors from server logs. > > What makes me to wonder is that why does archiver tries to copy > "000000010000000800000074.0066C9C0.backup" again when it's already > been archived. As soon I removed > "000000010000000800000074.0066C9C0.backup" from archive location, then > archiver was happy to copy again and moved on to archiving > 000000010000000800000074 etc. > > 2006-11-07 00:35:23 CST LOG: archived transaction log file > "000000010000000800000074.0066C9C0.backup" > 2006-11-07 00:35:23 CST LOG: archive command "test ! > -f /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup && > cp > pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" failed:return code 256 > > Any idea what may be going on here. > PG814, RH4.0 This was a bug fixed in 8.1.5 http://archives.postgresql.org/pgsql-committers/2006-06/msg00305.php I notice it isn't mentioned in the 8.1.5 release notes. You should upgrade. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
Added to 8.1.5 release notes:
<listitem><para>Fix rare bug in continuous archiving
(Tom)</para></listitem>
---------------------------------------------------------------------------
Simon Riggs wrote:
> On Tue, 2006-11-07 at 10:15 -0800, Subbiah, Stalin wrote:
>
> > Yesterday, we'd archiver problems in copying archived wal files from
> > pg_xlog to archive destination at the end of full hotbackup. Below are
> > the errors from server logs.
> >
> > What makes me to wonder is that why does archiver tries to copy
> > "000000010000000800000074.0066C9C0.backup" again when it's already
> > been archived. As soon I removed
> > "000000010000000800000074.0066C9C0.backup" from archive location, then
> > archiver was happy to copy again and moved on to archiving
> > 000000010000000800000074 etc.
> >
> > 2006-11-07 00:35:23 CST LOG: archived transaction log file
> > "000000010000000800000074.0066C9C0.backup"
> > 2006-11-07 00:35:23 CST LOG: archive command "test !
> > -f /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup &&
> > cp
> > pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup"
failed:return code 256
> >
> > Any idea what may be going on here.
>
> > PG814, RH4.0
>
> This was a bug fixed in 8.1.5
>
> http://archives.postgresql.org/pgsql-committers/2006-06/msg00305.php
>
> I notice it isn't mentioned in the 8.1.5 release notes. You should
> upgrade.
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
--
Bruce Momjian bruce@momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +