pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jim@nasby.net>
To: Subbiah, Stalin <SSubbiah@netopia.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Archive WAL Logs Failed
Date: Wed, 8 Nov 2006 00:26:11 -0600
Message-ID: <20061108062611.GZ90133@nasby.net> (raw)
In-Reply-To: <B949C470120CA7499A211214D76FBA5801C47AA6@mxca2.corp.netopia.com>
References: <B949C470120CA7499A211214D76FBA5801C47AA6@mxca2.corp.netopia.com>

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)



view thread (5+ messages)  latest in thread

Message-ID: <20061108062611.GZ90133@nasby.net>
Permalink:  ../20061108062611.GZ90133@nasby.net/
Also on:    postgresql.org/message-id/20061108062611.GZ90133@nasby.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jim@nasby.net, SSubbiah@netopia.com
  Subject: Re: Archive WAL Logs Failed
  In-Reply-To: <20061108062611.GZ90133@nasby.net>
  References: <B949C470120CA7499A211214D76FBA5801C47AA6@mxca2.corp.netopia.com> <20061108062611.GZ90133@nasby.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox