The defaulted value of "nobody" is for health_check_user in pgpool.conf, and must exist as a postgresql user in the backends. I changed it to postgres, and works fine. I don't use system_db, so I don't need a user for it. It's a matter of having the users in the backend engines, that's all.
Daniel > -----Original Message----- > From: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Glyn Astill > Sent: Thursday, February 12, 2009 1:13 PM > To: Tatsuo Ishii > Cc: pgpool-general@pgfoundry.org > Subject: Re: [Pgpool-general] PgPool2.2Beta2 and pgpoolAdmin-2.2-beta1 > > --- On Thu, 12/2/09, Tatsuo Ishii <is...@sraoss.co.jp> wrote: > > > > The login user and password for pgpoolAdmin is defined in > > pcp.conf. > > Not that login, I can login to the pgpoolAdmin page okay. > > It appears to use the user "pgpool" to check the and "nobody" > to check "Node status" and to access the cluster settings > "System DB" (which I don't use) > > I.e.: > > 2009-02-12 18:10:59 GMT [21371]: [1-1]: [user=pgpool]: > [host=127.0.0.1]: [db=pgpool]:: FATAL: database "pgpool" > does not exist > 2009-02-12 18:11:02 GMT [21377]: [1-1]: [user=nobody]: > [host=192.168.1.111]: [db=template1]:: FATAL: role "nobody" > does not exist > > > > _______________________________________________ > Pgpool-general mailing list > Pgpool-general@pgfoundry.org > http://pgfoundry.org/mailman/listinfo/pgpool-general > _______________________________________________ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general