Problem has been solved utilizing tcpdump which revealed that the standbys were
not trying to contact the primary server, although they each were contacting
the other standby. From
this, we determined that a minor typographical error was present in the
pgpool.conf file. The setting under the
Hi Jay,
Can you pls tell me how you resolved this issue.
We are running pgpool-II version 3.3.3
Thanks.
Ellen
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5818354.html
Sent from the PostgreSQL - general mailing list archive at
Ellen,
To date I have no solution. I'm currently trying to build a debug-able version
of 3.3.4 as I think I have a network problem which is preventing pgpool from
being a happy shareable system. Each one currently thinks it's a primary upon
startup, if it will start at all.
Sent from my iPad
Hi all,
If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
system being configured as master-slave, a socket file is created in /tmp,
and everything starts normally with no errors. If, however, I set
use_watchdog = on, pgpool will abort on startup with the following
Jay at Verizon wrote
Hi all,
If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
system being configured as master-slave, a socket file is created in /tmp,
and everything starts normally with no errors. If, however, I set
use_watchdog = on, pgpool will abort on
Hi all,
If I turn use_watchdog = off in the pgpool.conf file, then in spite of the
system being configured as master-slave, a socket file is created in /tmp,
and everything starts normally with no errors. If, however, I set
use_watchdog = on, pgpool will abort on startup with the following
