I guessed the master was in slave mode, because I thought configuration
file had no problem, and the FATAL message was written when the slave
connects to the master.
However, I think that slave's parameter:hot_standby is off, because you
can connect to the master.
Regards,
(13/09/13 0:58), AI Rumman wrote:
> Yes, I can access to the primary server perfectly.
>
>
>
>
> On Thu, Sep 12, 2013 at 11:55 AM, Suzuki Hironobu <hironobu@interdb.jp>wrote:
>
>> Hi,
>>
>>
>> (13/09/12 23:53), AI Rumman wrote:
>>
>>> Hi,
>>>
>>> I am trying to setup replication with Postgresql 9.2 in Ubuntu on Amazon
>>> Ec2.
>>> But stuck in the process.
>>> Postgresql standby log is showing:
>>>
>>> 2013-09-12 14:45:47 UTC LOG: entering standby mode
>>> 2013-09-12 14:45:47 UTC LOG: redo starts at 1/39000020
>>> 2013-09-12 14:45:47 UTC LOG: record with zero length at 1/3905C088
>>> 2013-09-12 14:45:47 UTC LOG: streaming replication successfully connected
>>> to primary
>>> 2013-09-12 14:45:47 UTC LOG: consistent recovery state reached at
>>> 1/391C8588
>>>
>>> But ,
>>> psql
>>> 2013-09-12 14:48:04 UTC FATAL: the database system is starting up
>>>
>>> I configured replication for Centos so many times and followed those
>>> steps.
>>> Is there something I am missing?
>>>
>>> Thanks.
>>>
>>>
>> This FATAL message is returned when the status of primary server is
>> PM_STARTUP or PM_RECOVERY.
>> I guess your primary server is in startup state.
>> Can you access to the primary server using psql? Please check the primary
>> server.
>>
>>
>> Regards,
>>
>>
>>
>>
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>> To make changes to your subscription:
>> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general>
>>
