> We're using pgpool-II 2.3.3 purely as a connection pool to postgres 8.4, > however if any one of the connections are closed via pg_terminate_backend in > postgres 8.4 then pgpool attempts to fail over to a nonexistant node? See > logging below. > > Also how do we log when pgpool is run as a daemon? The only way I could get > the log output was to run with -n. > > Thanks > Glyn > > 2010-05-10 12:48:13 LOG: pid 31815: pgpool-II successfully started. version > 2.3.3 (tomiteboshi) > 2010-05-10 12:49:20 LOG: pid 31815: reload config files. > 2010-05-10 12:50:06 LOG: pid 31819: postmaster on DB node 0 was shutdown by > administrative command > 2010-05-10 12:50:06 LOG: pid 31819: notice_backend_error: 0 fail over > request from pid 31819 > 2010-05-10 12:50:06 LOG: pid 31815: starting degeneration. shutdown host > 10.10.10.95(5432) > 2010-05-10 12:50:06 ERROR: pid 31815: failover_handler: no valid DB node found > 2010-05-10 12:50:06 LOG: pid 31815: failover_handler: set new master node: 1 > 2010-05-10 12:50:06 LOG: pid 31815: failover done. shutdown host > 10.10.10.95(5432) > 2010-05-10 12:50:14 LOG: pid 32465: Cannot accept() new connection. all > backends are down
I couldn't reproduce your problem (although I tested with replication mode). Can you show me pgpool.conf? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general