Archive WAL Logs Failed

This is a multi-part message in MIME format.

------_=_NextPart_001_01C70298.A494895F
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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.ba ckup && cp
pg_xlog/000000010000000800000074.0066C9C0.backup
/b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup"
failed: return code 256

Any idea what may be going on here.

Thanks,
Stalin

PG814, RH4.0




------_=_NextPart_001_01C70298.A494895F
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">
<TITLE>Archive WAL Logs Failed</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Verdana">Hi All,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">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.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">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.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">2006-11-07 00:35:23 CST  =
LOG:  archived transaction log file =
"000000010000000800000074.0066C9C0.backup"</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Verdana">2006-11-07 00:35:23 CST  =
LOG:  archive command "test ! -f =
/b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup =
&& cp pg_xlog/000000010000000800000074.0066C9C0.backup =
/b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup " =
failed: return code 256</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">Any idea what may be going on =
here.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">Thanks,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Verdana">Stalin</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Verdana">PG814, RH4.0</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C70298.A494895F--
SSubbiah [ Di, 07 November 2006 19:15 ] [ ID #1527038 ]

Re: 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.ba ckup && cp
> pg_xlog/000000010000000800000074.0066C9C0.backup
> /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup"
> failed: return code 256
>
> Any idea what may be going on here.
>
> Thanks,
> Stalin
>
> PG814, RH4.0
>
>
>

--
Jim Nasby jim [at] 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
Jim Nasby [ Mi, 08 November 2006 07:26 ] [ ID #1528313 ]

Re: Archive WAL Logs Failed

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 [at] postgresql.org
[mailto:pgsql-admin-owner [at] postgresql.org] On Behalf Of Jim C. Nasby
Sent: Tuesday, November 07, 2006 10:26 PM
To: Subbiah, Stalin
Cc: pgsql-admin [at] 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.ba ckup && cp

> pg_xlog/000000010000000800000074.0066C9C0.backup
> /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup"
> failed: return code 256
>
> Any idea what may be going on here.
>
> Thanks,
> Stalin
>
> PG814, RH4.0
>
>
>

--
Jim Nasby jim [at] 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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
SSubbiah [ Di, 14 November 2006 21:43 ] [ ID #1535120 ]

Re: Archive WAL Logs Failed

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.ba ckup &&
> cp
> pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup" 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/msg0 0305.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
Simon Riggs [ Sa, 18 November 2006 10:40 ] [ ID #1540329 ]

Re: Archive WAL Logs Failed

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.ba ckup &&
> > cp
> > pg_xlog/000000010000000800000074.0066C9C0.backup /b01/pgdata/archive/db1/000000010000000800000074.0066C9C0.ba ckup" 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/msg0 0305.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 [at] momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
Bruce Momjian [ Do, 23 November 2006 04:31 ] [ ID #1545475 ]
Datenbanken » gmane.comp.db.postgresql.admin » Archive WAL Logs Failed

Vorheriges Thema: Converting CP1252 to UTF-8
Nächstes Thema: PGSQL manager password lost.