Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id 9EC989FA469 for ; Wed, 8 Nov 2006 02:26:15 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.60]) (amavisd-new, port 10024) with ESMTP id 93781-01 for ; Wed, 8 Nov 2006 02:26:14 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 89E869F9425 for ; Wed, 8 Nov 2006 02:26:14 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id E017556468; Wed, 8 Nov 2006 00:26:13 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Wed, 8 Nov 2006 00:26:11 -0600 Date: Wed, 8 Nov 2006 00:26:11 -0600 From: "Jim C. Nasby" To: "Subbiah, Stalin" Cc: pgsql-admin@postgresql.org Subject: Re: Archive WAL Logs Failed Message-ID: <20061108062611.GZ90133@nasby.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:061108:ssubbiah@netopia.com::eQTzpW8S21TGpFgl:00000000000000000 00000000000000000000000094ek X-Hashcash: 1:20:061108:pgsql-admin@postgresql.org::k1aznxhs+zn7nTZj:00000000000 00000000000000000000000057Zd X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/69 X-Sequence-Number: 23596 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)