[pgpool-general: 2555] Re: pgpoll failure

[Gonzalo Gil]

i send the message but it was too long.
i'll attach the files....

it happens again, even when node 2 was the postgres standby node.

after i put the logs here, i shutdown node 1 (it has the primary database)
and it happens the same thing. node 2 lost ip and no failover happens.


TKS!




On Mon, Feb 10, 2014 at 5:23 AM, Yugo Nagata <nagata at sraoss.co.jp> wrote:

> Hi,
>
> This is odd that pgpool-1 losts VIP when server2 goes down. For analysis,
> could you please send pgpool.conf and log output (of both pgpool1 and
> pgpool2)?
>
> On Tue, 4 Feb 2014 13:38:16 -0200
> Gonzalo Gil <gonxalo2000 at gmail.com> wrote:
>
> > Hello Tatsuo Ishii. I send some query mails to
> > pgpool-general at pgpool.netbut i don't get my own messagese. But i do
> > recieve other mails from the
> > forum.
> >
> > Can you answer me some questions or forward them to the forum!?
> >
> >
> > I'm runing pgpool with streaming replication: pgpool1 - db postgres1
> > (server 1) and pgpool2 - db postgres 2 (server 2).
> > I'm using watchdog with a virtual ip and life_check_query.
> >
> > It's all configured and working .... more or less....
> >
> > INIT: I start my system: postgres1 is standby database and postgres2
> > is master (streaming replication).
> > pgpool1 has the virtual ip.(and pgpool2 no, obviously)
> >
> > i connect to database via pgpool and everithing is ok.
> > i stop postgres1 and nothing happens because i check new_master <>
> > old_master (no master failure).
> > i start postgres1 again (and returning it with pgpoolAdmin) or call a
> > recovery and it works great.
> >
> > I stop postgres2 and failover fires ... and i get postgres1 as the new
> > primary.
> > and so on...
> >
> > this works fine.
> >
> >
> > i go back to INIT again....
> > and i do in server2
> > reboot -h now
> >
> > i see in the server1 (pgpool1) log that pgpool2 is down...ok
> > watching the log, i see pgpool1 lost the virtual ip address (!?)....and
> > tell me to restart pgpool....(!?)
> >
> > i restart it and i see that failover fires ... but in the failover
> script i
> > get new_master_node = old_master_node ...and thus i do not make touch and
> > postgres1 keeps as a standby...
> >
> >
> > I change failover.sh (and the command in the pgpool.conf). i include all
> > parameters to see it's values when failover.sh start....
> >
> > Then, i restart serve2 and "return" database to pgpool....
> >
> > again, pgpool1 has the virtual ip.
> > i stop database in node 2 and failover fires.... but pgpool2 does
> it....and
> > pgpool1 too (!?)
> > i check network activity and saw that pgpool2 connects to server1 and
> make
> > the touch and i did see log from pgpool1 firing the failover command
> too....
> >
> >
> >
> > Cuestions....
> > 1. why pgpool1 lost virtual ip and ask me to restart!?
> > 2. why pgpool2 fires failover? i thought just the "primary" pgpool (the
> one
> > with the virtual ip) fires it.
> >
> >
> > i hope you understand mr.
> > tks a lot for your time..
> > sorry for my english.
>
>
> --
> Yugo Nagata <nagata at sraoss.co.jp>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140210/9b699fab/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool_log_conf.7z
Type: application/x-7z-compressed
Size: 136770 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20140210/9b699fab/attachment-0001.bin>