Hi, From: "Bruno Lustosa" <[EMAIL PROTECTED]> Subject: Re: [Pgpool-general] Zombies roaming the server Date: Tue, 19 Feb 2008 10:50:33 -0300
> There are lots of these between 04:14 and 05:12. Really lots. > > 2008-02-19 04:14:06 ERROR: pid 8547: pool_check_fd: data is not ready > tp->tv_sec 5 tp->tp_usec 5000000 > 2008-02-19 04:14:06 ERROR: pid 8547: pool_read: pool_check_fd failed (Success) > 2008-02-19 04:14:06 ERROR: pid 8547: pool_process_query: failed to > read kind from 0 th backend > 2008-02-19 04:14:06 LOG: pid 8547: do_child: exits with status 1 due to > error I've fixed by the following commit. http://lists.pgfoundry.org/pipermail/pgpool-committers/2008-February/000647.html replication_strict parameter was removed in pgpool-II 2.0. However, replication_timeout was not removed. > After that, the database goes offline with messages like this (there > are a few of the previous too): > > 2008-02-19 05:12:44 ERROR: pid 10141: pool_read_kind: kind does not > match between master(69) slot[1] (83) > 2008-02-19 05:12:44 ERROR: pid 10141: pool_do_auth: failed to read > kind before BackendKeyData It seems that client authentication was failed on backend_hostname0. Could you show me PostgreSQL's log file on backend_hostname0? Regards, -- Yoshiyuki Asaba [EMAIL PROTECTED] _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
