Received: from localhost (uranus.hub.org [200.46.204.60]) by postgresql.org (Postfix) with ESMTP id 7149E9FA5C8 for ; Tue, 14 Nov 2006 16:42:01 -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 12972-09 for ; Tue, 14 Nov 2006 16:41:58 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id BF97D9FA4C9 for ; Tue, 14 Nov 2006 16:41:58 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mxca2.corp.netopia.com (mx-us-west.netopia.com [65.206.239.221]) by svr4.postgresql.org (Postfix) with ESMTP id EED1D5AF03F for ; Tue, 14 Nov 2006 20:41:57 +0000 (GMT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Re: Archive WAL Logs Failed Date: Tue, 14 Nov 2006 12:43:02 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] Archive WAL Logs Failed Thread-Index: AccC/v0mPFLH0zM6T0C9v1xYBTY19QFLeK+w From: "Subbiah, Stalin" To: "Jim C. Nasby" Cc: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/146 X-Sequence-Number: 23673 Nope. Only archiver does that.=20 Since we had this problem the backups are running just fine and no problems whatsoever with archiver either. Strange!!!=20 -----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, >=20 > Yesterday, we'd archiver problems in copying archived wal files from=20 > 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=20 > "000000010000000800000074.0066C9C0.backup" again when it's already=20 > 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. >=20 > 2006-11-07 00:35:23 CST LOG: archived transaction log file=20 > "000000010000000800000074.0066C9C0.backup" > 2006-11-07 00:35:23 CST LOG: archive command "test ! -f=20 > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup && cp > pg_xlog/000000010000000800000074.0066C9C0.backup > /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.backup" > failed: return code 256 >=20 > Any idea what may be going on here. >=20 > Thanks, > Stalin >=20 > PG814, RH4.0 >=20 >=20 >=20 --=20 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