Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 52D749F9FE2 for ; Sat, 18 Nov 2006 05:41:54 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 71880-07 for ; Sat, 18 Nov 2006 05:41:50 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 1E69C9F9FB2 for ; Sat, 18 Nov 2006 05:41:49 -0400 (AST) thread-index: AccK9cZjuBQ0KzWoRYeEYDRerlThhQ== Received: from [192.168.0.31] ([84.12.80.212]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 18 Nov 2006 04:41:50 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 Content-class: urn:content-classes:message Importance: normal Subject: Re: Archive WAL Logs Failed From: "Simon Riggs" To: "Subbiah, Stalin" Cc: In-Reply-To: References: Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 18 Nov 2006 09:40:59 +0000 Message-ID: <1163842859.27956.737.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Nov 2006 09:41:51.0250 (UTC) FILETIME=[C63CFF20:01C70AF5] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/181 X-Sequence-Number: 23708 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