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 watchdog section for other_hostname0 was correct, and other required settings for that entry were also correct, but had somehow been commented out. The log file was not very revealing, and finding one badly inserted "#" in a 647 line file was problematic to say the least.
On 9/9/2014 2:42 PM, Ellen [via PostgreSQL] wrote: > Hi Jay, > Can you pls tell me how you resolved this issue. > We are running pgpool-II version 3.3.3 > Thanks. > Ellen > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5818354.html > To unsubscribe from Pgpool starting problem, click here > <http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5803276&code=amF5a25vd3N1bml4QGdtYWlsLmNvbXw1ODAzMjc2fDM1NDE5ODU4OQ==>. > NAML > <http://postgresql.1045698.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > -- View this message in context: http://postgresql.1045698.n5.nabble.com/Pgpool-starting-problem-tp5803276p5819090.html Sent from the PostgreSQL - general mailing list archive at Nabble.com.
