Thanks for your reply. That doesn't appear to be the problem. While logged onto the server where pgpool is running, I can successfully invoke psql to connect directly to both of the standby servers (using port 5432). Also, I'm not seeing any errors in the pgpool log, where I'd expect to see something if connection attempts were failing?
On Sun, Sep 4, 2011 at 4:43 PM, Richard Diekema <rdiek...@gmail.com> wrote: > If I recall, unexpected EOF means your connection to one of the postgres > instances is failing. Check your pg_hba.conf to make sure the pgpool has > permission to connect, and that you can connect from the server running > pgpool. > > On Sep 4, 2011 7:22 PM, "Lonni J Friedman" <netll...@gmail.com> wrote: >> No one has any ideas or suggestions? >> >> On Fri, Sep 2, 2011 at 6:44 PM, Lonni J Friedman <netll...@gmail.com> >> wrote: >>> Greetings, >>> I just deployed a postgresql-9.0.4 cluster (1 master, 2 hot >>> standby's), with pgpool-II-3.0.4 (all running on Linux-x86_64 >>> servers). I'm currently only using pgpool for load balancing, and its >>> working fine. However, I'm see tons (dozens every minute) of the >>> following in my postgresql server logs: >>> LOG: unexpected EOF on client connection >>> >>> This was not happening prior to setting up pgpool, so I'm currently >>> working with the assumption that something in pgpool's load balancing >>> might be causing it. Is this a known issue? If not, how can I debug >>> this further? _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
