Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 770279FB216 for ; Wed, 22 Nov 2006 23:31:12 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 47722-10 for ; Wed, 22 Nov 2006 23:31:04 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 993679FB20D for ; Wed, 22 Nov 2006 23:31:09 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id kAN3V0T07467; Wed, 22 Nov 2006 22:31:00 -0500 (EST) From: Bruce Momjian Message-Id: <200611230331.kAN3V0T07467@momjian.us> Subject: Re: Archive WAL Logs Failed In-Reply-To: <1163842859.27956.737.camel@silverbirch.site> To: Simon Riggs Date: Wed, 22 Nov 2006 22:31:00 -0500 (EST) CC: "Subbiah, Stalin" , pgsql-admin@postgresql.org X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/206 X-Sequence-Number: 23733 Added to 8.1.5 release notes: Fix rare bug in continuous archiving (Tom) --------------------------------------------------------------------------- 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. +