Em..weird. This is the only log that I can find in the 192.168.1.136 postgresql database.<div><br></div><div>And when I click the recovery button, it still running as primary server</div><div><br></div><div>Aside from that,I could not find ANY log for pgpool server.</div>
<div><br></div><div>The default folder on pgpool server is on /var/log/pgpool/ am I right?</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Fri, Nov 9, 2012 at 3:32 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im HOEnZb">Unfortunately this is not the log I wanted. Can you try online<br>
recovery again and send the standby PostgreSQL log?<br>
</div><div class="HOEnZb"><div class="h5">--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese: <a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_is_in_recovery()<br>
> .<br>
> .<br>
> .<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
> LOG: statement: SELECT pg_last_xlog_replay_location()<br>
><br>
> That is for today's logs.<br>
> And the output is similar to any other date since I'm setting this<br>
> postgresql with pgpool.<br>
><br>
><br>
> On Fri, Nov 9, 2012 at 2:55 PM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> wrote:<br>
><br>
>> It seems PostgreSQL on 192.168.1.136 accidentaly started up as a<br>
>> primary server. Can you show us PostgreSQL log when it came up?<br>
>> -<br>
>> Tatsuo Ishii<br>
>> SRA OSS, Inc. Japan<br>
>> English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
>> Japanese: <a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
>><br>
>> > Hi Tatsuo san,<br>
>> ><br>
>> > Anyway I've already figured out the problem.<br>
>> > It seems that I've mistakenly configured wrong setting in pgpool conf.<br>
>> ><br>
>> > But new problem arise when I'm solving this problem.<br>
>> ><br>
>> > IP Address Port Status<br>
>> > Weight<br>
>> > 192.168.1.134 5432 UP.DISCONNECT.RUNNING AS PRIMARY SERVER<br>
>> > 0.500<br>
>> > 192.168.1.136 5432 UP.DISCONNECT.RUNNING AS PRIMARY SERVER<br>
>> > 0.500<br>
>> ><br>
>> > I want to make the postgreSQL in 192.168.1.134 as primary server whereas<br>
>> > the 192.168.1.136 as standby server.<br>
>> > I'm using master/slave stream replication and follow exactly as your<br>
>> > documentation here (exclude the hostname and pasword) :<br>
>> ><br>
>> <a href="http://www.pgpool.net/pgpool-web/contrib_docs/simple_sr_setting2/index.html" target="_blank">http://www.pgpool.net/pgpool-web/contrib_docs/simple_sr_setting2/index.html</a><br>
>> ><br>
>> > Can you help me.Why it is showing this status?<br>
>> ><br>
>> ><br>
>> > On Fri, Nov 9, 2012 at 1:00 PM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>><br>
>> wrote:<br>
>> ><br>
>> >> > Hi all,<br>
>> >> ><br>
>> >> > I'm facing new problem when configuring my pgpoolAdmin-3.2.1<br>
>> >> ><br>
>> >> > When I go to the node info it show the this status :<br>
>> >> ><br>
>> >> > IP Address Port Status Weight<br>
>> >> ><br>
>> >> > 192.168.1.134 5432 UP 0.500<br>
>> >> ><br>
>> >> ><br>
>> >> > When I click the disconnect button, it show this status :<br>
>> >> ><br>
>> >> > IP Address Port Status Weight<br>
>> >> ><br>
>> >> > 192.168.1.134 5432 DOWN 0.500<br>
>> >> ><br>
>> >> ><br>
>> >> > But when I click the recovery button, it showing this kind of error<br>
>> >> ><br>
>> >> ><br>
>> >> > Error Code e1010<br>
>> >> > Error Message pcp_attach_node command error occurred.<br>
>> >> ><br>
>> >> > Can someone explain what might cause this to happened?<br>
>> >><br>
>> >> Please make sure that PostgreSQL on 192.168.1.134 is up and<br>
>> >> running. If you are sure, please show us the pgpool log and PostgreSQL<br>
>> >> log of 192.168.1.134.<br>
>> >> --<br>
>> >> Tatsuo Ishii<br>
>> >> SRA OSS, Inc. Japan<br>
>> >> English: <a href="http://www.sraoss.co.jp/index_en.php" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
>> >> Japanese: <a href="http://www.sraoss.co.jp" target="_blank">http://www.sraoss.co.jp</a><br>
>> >><br>
>><br>
</div></div></blockquote></div><br></div>