On Tue, Jan 25, 2011 at 8:59 PM, Khadtare, Sharad
<sharad.khadtare@teamaol.com> wrote:
> Pls find below logfile of standby and recovery.conf in standby data direc=
tory.
>
> bash-3.2$ cat logfile
> LOG: =A0database system was interrupted while in recovery at log time 201=
1-01-25 05:28:35 EST
> HINT: =A0If this has occurred more than once some data might be corrupted=
and you might need to choose an earlier recovery target.
> LOG: =A0entering standby mode
> LOG: =A0restored log file "000000010000000000000037" from archive
> LOG: =A0redo starts at 0/37000020
> LOG: =A0consistent recovery state reached at 0/38000000
> LOG: =A0database system is ready to accept read only connections
> cp: cannot stat `/db/postgres/archive/000000010000000000000038': No such =
file or directory
> LOG: =A0unexpected pageaddr 0/30000000 in log file 0, segment 56, offset 0
> cp: cannot stat `/db/postgres/archive/000000010000000000000038': No such =
file or directory
> LOG: =A0trigger file found: /db/postgres/trigger
The above message means that you created the trigger file and
promoted the standby server to the master. Since the standby
was running as the master, walreceiver was not invoked in the
standby.
To start replication, you need to create the standby (taking the
base backup from the master is required) and start it after you
*ensure* that there is no trigger file in the standby.
I hope this helps..
Regards,
--=20
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
