[pgpool-general: 1193] Re: need help : error code e1010

[Nozomi Anzai]

Hi,

> Em..weird. This is the only log that I can find in the 192.168.1.136
> postgresql database.
> 
> And when I click the recovery button, it still running as primary server
> 
> Aside from that,I could not find ANY log for pgpool server.
> 
> The default folder on pgpool server is on /var/log/pgpool/  am I right?

See "pgpool log destination" in pgpoolAdmin's config page.
http://_your_server_/_pgpooladmin_path_/config.php


> 
> 
> On Fri, Nov 9, 2012 at 3:32 PM, Tatsuo Ishii <ishii ¡÷ postgresql.org> wrote:
> 
> > Unfortunately this is not the log I wanted.  Can you try online
> > recovery again and send the standby PostgreSQL log?
> > --
> > Tatsuo Ishii
> > SRA OSS, Inc. Japan
> > English: http://www.sraoss.co.jp/index_en.php
> > Japanese: http://www.sraoss.co.jp
> >
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_is_in_recovery()
> > > .
> > > .
> > > .
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > > LOG:  statement: SELECT pg_last_xlog_replay_location()
> > >
> > > That is for today's logs.
> > > And the output is similar to any other date since I'm setting this
> > > postgresql with pgpool.
> > >
> > >
> > > On Fri, Nov 9, 2012 at 2:55 PM, Tatsuo Ishii <ishii ¡÷ postgresql.org>
> > wrote:
> > >
> > >> It seems PostgreSQL on 192.168.1.136 accidentaly started up as a
> > >> primary server.  Can you show us PostgreSQL log when it came up?
> > >> -
> > >> Tatsuo Ishii
> > >> SRA OSS, Inc. Japan
> > >> English: http://www.sraoss.co.jp/index_en.php
> > >> Japanese: http://www.sraoss.co.jp
> > >>
> > >> > Hi Tatsuo san,
> > >> >
> > >> > Anyway I've already figured out the problem.
> > >> > It seems that I've mistakenly configured wrong setting in pgpool conf.
> > >> >
> > >> > But new problem arise when I'm solving this problem.
> > >> >
> > >> > IP Address           Port    Status
> > >> >                                     Weight
> > >> > 192.168.1.134      5432     UP.DISCONNECT.RUNNING AS PRIMARY SERVER
> > >> >  0.500
> > >> > 192.168.1.136      5432     UP.DISCONNECT.RUNNING AS PRIMARY SERVER
> > >> >  0.500
> > >> >
> > >> > I want to make  the postgreSQL in 192.168.1.134 as primary server
> > whereas
> > >> > the 192.168.1.136 as standby server.
> > >> > I'm using master/slave stream replication and follow exactly as your
> > >> > documentation here (exclude the hostname and pasword) :
> > >> >
> > >>
> > http://www.pgpool.net/pgpool-web/contrib_docs/simple_sr_setting2/index.html
> > >> >
> > >> > Can you help me.Why it is showing this status?
> > >> >
> > >> >
> > >> > On Fri, Nov 9, 2012 at 1:00 PM, Tatsuo Ishii <ishii ¡÷ postgresql.org>
> > >> wrote:
> > >> >
> > >> >> > Hi all,
> > >> >> >
> > >> >> > I'm facing new problem when configuring my pgpoolAdmin-3.2.1
> > >> >> >
> > >> >> > When I go to the node info it show the this status :
> > >> >> >
> > >> >> > IP Address           Port    Status   Weight
> > >> >> >
> > >> >> > 192.168.1.134      5432     UP        0.500
> > >> >> >
> > >> >> >
> > >> >> > When I click the disconnect button, it show this status :
> > >> >> >
> > >> >> > IP Address           Port    Status   Weight
> > >> >> >
> > >> >> > 192.168.1.134      5432     DOWN        0.500
> > >> >> >
> > >> >> >
> > >> >> > But when I click the recovery button, it showing this kind of error
> > >> >> >
> > >> >> >
> > >> >> > Error Code  e1010
> > >> >> > Error Message pcp_attach_node command error occurred.
> > >> >> >
> > >> >> > Can someone explain what might cause this to happened?
> > >> >>
> > >> >> Please make sure that PostgreSQL on 192.168.1.134 is up and
> > >> >> running. If you are sure, please show us the pgpool log and
> > PostgreSQL
> > >> >> log of 192.168.1.134.
> > >> >> --
> > >> >> Tatsuo Ishii
> > >> >> SRA OSS, Inc. Japan
> > >> >> English: http://www.sraoss.co.jp/index_en.php
> > >> >> Japanese: http://www.sraoss.co.jp
> > >> >>
> > >>
> >


-- 
Nozomi Anzai
SRA OSS, Inc. Japan