Re: Hot Standby pg_xlog problem

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Blake <postgresql(at)akunno(dot)net>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Hot Standby pg_xlog problem
Date: 2010-12-15 00:05:17
Message-ID: AANLkTikuex0rNA4fVjLRa-vxdzmfpAZPffzUgjNn0xA1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 15, 2010 at 7:24 AM, Michael Blake <postgresql(at)akunno(dot)net> wrote:
> I'm trying to set up a master/slave server, which initially worked
> fine, but recently started failing with the following error:
>
> ==============
> LOG:  database system was interrupted; last known up at [time]
> LOG:  could not open file "pg_xlog/00000001000000000000002B" (log file
> 0, segment 43): No such file or directory
> LOG:  invalid checkpoint record
> PANIC:  could not locate required checkpoint record
> HINT:  If you are not restoring from a backup, try removing the file
> "/var/lib/postgresql/9.0/main/backup_label".
> LOG:  startup process (PID 31489) was terminated by signal 6: Aborted
> LOG:  aborting startup due to startup process failure
> ==============

If you set standby_mode to on in recovery.conf, you should get
the following message before getting PANIC, but that isn't in your
log messages.

LOG: entering standby mode

So I guess you forgot placing recovery.conf in HS server.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Carlos Mennens 2010-12-15 00:08:33 Understanding Schema's
Previous Message Devrim GÜNDÜZ 2010-12-14 23:30:46 Re: Hot Standby pg_xlog problem