pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Archive WAL Logs Failed
5+ messages / 4 participants
[nested] [flat]

* Archive WAL Logs Failed
@ 2006-11-07 18:15  Subbiah, Stalin <SSubbiah@netopia.com>
  0 siblings, 2 replies; 5+ messages in thread

From: Subbiah, Stalin @ 2006-11-07 18:15 UTC (permalink / raw)
  To: pgsql-admin

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

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Archive WAL Logs Failed
@ 2006-11-08 06:26  Jim C. Nasby <jim@nasby.net>
  parent: Subbiah, Stalin <SSubbiah@netopia.com>
  1 sibling, 0 replies; 5+ messages in thread

From: Jim C. Nasby @ 2006-11-08 06:26 UTC (permalink / raw)
  To: Subbiah, Stalin <SSubbiah@netopia.com>; +Cc: pgsql-admin

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)



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Archive WAL Logs Failed
@ 2006-11-14 20:43  Subbiah, Stalin <SSubbiah@netopia.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Subbiah, Stalin @ 2006-11-14 20:43 UTC (permalink / raw)
  To: Jim C. Nasby <jim@nasby.net>; +Cc: pgsql-admin

Nope. Only archiver does that. 

Since we had this problem the backups are running just fine and no
problems whatsoever with archiver either. Strange!!! 

-----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,
> 
> 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)

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

                http://www.postgresql.org/about/donate



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Archive WAL Logs Failed
@ 2006-11-18 09:40  Simon Riggs <simon@2ndquadrant.com>
  parent: Subbiah, Stalin <SSubbiah@netopia.com>
  1 sibling, 1 reply; 5+ messages in thread

From: Simon Riggs @ 2006-11-18 09:40 UTC (permalink / raw)
  To: Subbiah, Stalin <SSubbiah@netopia.com>; +Cc: pgsql-admin

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





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Archive WAL Logs Failed
@ 2006-11-23 03:31  Bruce Momjian <bruce@momjian.us>
  parent: Simon Riggs <simon@2ndquadrant.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Bruce Momjian @ 2006-11-23 03:31 UTC (permalink / raw)
  To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Subbiah, Stalin <SSubbiah@netopia.com>; pgsql-admin


Added to 8.1.5 release notes:

	<listitem><para>Fix rare bug in continuous archiving
	(Tom)</para></listitem>


---------------------------------------------------------------------------

 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. +



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2006-11-23 03:31 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-11-07 18:15 Archive WAL Logs Failed Subbiah, Stalin <SSubbiah@netopia.com>
2006-11-08 06:26 ` Jim C. Nasby <jim@nasby.net>
2006-11-18 09:40 ` Simon Riggs <simon@2ndquadrant.com>
2006-11-23 03:31   ` Bruce Momjian <bruce@momjian.us>
2006-11-14 20:43 Re: Archive WAL Logs Failed Subbiah, Stalin <SSubbiah@netopia.com>

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