Pgpool Issue- - Mailing list pgsql-admin

Hi All,

I have installed Postgres 8.3.3 and Pgpool 2.2RC2 on two machines and Both servers have the identical copy of the database running.
I have started postgres server on both machines and I have started pgpool on both machines.

But for some reasons i am not able to connect to database through pgpool.
psql -U postgres -p 9999

Pgpool logs for the first machine shows

2009-02-25 18:00:31 LOG:   pid 30544: pgpool successfully started
2009-02-25 18:04:27 LOG:   pid 30555: connection received: host=[local]
2009-02-25 18:04:27 ERROR: pid 30555: pool_read_kind: kind does not match between master(82) slot[1] (69)
2009-02-26 10:56:19 ERROR: pid 30544: connect_inet_domain_socket: connect() failed: Connection refused
2009-02-26 10:56:19 ERROR: pid 30544: health check failed. 1 th host fdbr-res0002 at port 5432 is down
2009-02-26 10:56:19 LOG:   pid 30544: set 1 th backend down status
2009-02-26 10:56:19 LOG:   pid 30544: starting degeneration. shutdown host fdbr-res0002(5432)
2009-02-26 10:56:19 LOG:   pid 30544: failover_handler: set new master node: 0
2009-02-26 10:56:19 LOG:   pid 30544: failover done. shutdown host fdbr-res0002(5432)
pid file found. is another pgpool(30544) is running?
2009-02-26 10:58:03 ERROR: pid 30544: connect_inet_domain_socket: connect() failed: Connection refused
2009-02-26 10:58:03 ERROR: pid 30544: health check failed. 0 th host localhost at port 5432 is down
2009-02-26 10:58:03 LOG:   pid 30544: set 0 th backend down status
2009-02-26 10:58:03 LOG:   pid 30544: starting degeneration. shutdown host localhost(5432)
2009-02-26 10:58:03 ERROR: pid 30544: failover_handler: no valid DB node found
2009-02-26 10:58:03 LOG:   pid 30544: failover_handler: set new master node: 2
2009-02-26 10:58:03 LOG:   pid 30544: failover done. shutdown host localhost(5432)
pid file found. is another pgpool(30544) is running?
2009-02-26 11:44:11 LOG:   pid 7900: Cannot accept() new connection. all backends are down
2009-02-26 11:45:59 LOG:   pid 21707: Cannot accept() new connection. all backends are down
2009-02-26 11:46:25 LOG:   pid 30544: received fast shutdown request
stop request sent to pgpool. waiting for termination....done.


I can connect to individual database using
"psql -U postgres -p 5432" --> fdbr-res0001
"psql -U postgres -p 5432" --> fdbr-res0002

Here is the configuration of Pgpool.conf file, both machines have the same identical configuration file with only backend_hostname1 = 'fdbr-res0002' difference

listen_addresses = '*'
port = 9999
pcp_port = 9898
socket_dir = '/tmp'
pcp_socket_dir = '/tmp'
backend_socket_dir = '/tmp'
pcp_timeout = 10
num_init_children = 64
max_pool = 10
child_life_time = 300
connection_life_time = 0
child_max_connections = 0
client_idle_limit = 0
authentication_timeout = 60
logdir = '/usr/pgpool-II/2.2RC2/log'
pid_file_name = '/usr/pgpool-II/2.2RC2/etc/pgpool.pid'
replication_mode = true
load_balance_mode = true
replication_stop_on_mismatch = false
replicate_select = false
reset_query_list = 'ABORT; RESET ALL; SET SESSION AUTHORIZATION DEFAULT'
print_timestamp = true
master_slave_mode = false
connection_cache = true
health_check_timeout = 20
health_check_period = 1
health_check_user = 'postgres'
failover_command = ''
failback_command = ''
insert_lock = false
ignore_leading_white_space = true
log_statement = true
log_connections = true
log_hostname = true
parallel_mode = false
enable_query_cache = false
#pgpool2_hostname = 'fdbr-res0002'
pgpool2_hostname = ''
system_db_hostname = 'localhost'
system_db_port = 5432
system_db_dbname = 'pgpool'
system_db_schema = 'pgpool_catalog'
system_db_user = 'pgpool'
system_db_password = ''

backend_hostname0 = 'localhost'
backend_port0 = 5432
backend_weight0 = 1
backend_data_directory0 = '/mnt/data/pns/pgsql8.3.6'

backend_hostname1 = 'fdbr-res0002'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/mnt/data/pns/pgsql8.3.6'

enable_pool_hba = true
recovery_user = 'postgres'
recovery_password = ''
recovery_1st_stage_command = ''
recovery_2nd_stage_command = ''
recovery_timeout = 90
client_idle_limit_in_recovery = 0


Any solution would be greatly appreciated

Thanks
Deepak Murthy