On Mon, Jul 13, 2009 at 6:06 AM, Sridhar Reddapani<[email protected]> wrote:
> 2009-07-13 11:54:03 DEBUG: pid 785: health_check: 0 th DB node status: 2 > 2009-07-13 11:54:03 DEBUG: pid 785: health_check: 1 th DB node status: 2 Sounds good so far... > 2009-07-13 11:54:55 ERROR: pid 5587: pool_read: read failed (Connection > reset by peer) Looks like one of your PostgreSQL servers is playing. I would check the configuration of that node (everything in it), because something is wrong. I cannot really provide any more information with the log you provide, but I've had this error before, too. I would also check that the clients connecting to the cluster are doing it properly (including closing connections). > 2009-07-13 11:54:55 LOG: pid 5587: notice_backend_error: 1 fail over > request from pid 5587 > 2009-07-13 11:54:55 ERROR: pid 5587: pool_flush_it: write failed (Broken > pipe) offset: 0 wlen: 5 First time I see this error, so I cannot say anything beyond what's obvious (what the message says). > 2009-07-13 11:54:55 DEBUG: pid 785: failover_handler called [..] > 2009-07-13 11:54:55 DEBUG: pid 788: child receives shutdown request signal 3 Normal degeneration of a node... -- Jaume Sabater http://linuxsilo.net/ "Ubi sapientas ibi libertas" _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
