Please provide logging of pgpool and PostgreSQL when the problem occured. In the mean time, I don't see particular problem with PostgreSQL 8.3.9 and pgpool-II 3.0.3 combo. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp
> Hello, I need anyone help me!!! > > I'm pretty new working with cluster tools. I've a 4 node scheme to > ensure high availability, replication, connection pooling and load > balancing, 2 nodes are balancers and 2 are SQL(backends). Each > balancer has an instance of pgPool-II 3.0.3 and Heartbeat 2.1.3. the > SQL nodes have an instance of PostgreSQL 8.3.9. All of this solution > is on CentOS 5.5 operating system. > The pgPool-II service is monitoring by Heartbeat. The problem is, that > every morning after the servers are kept in a specific time without > attending requests, PGPool service's stop and every morning database > servers are down. > I need someone who can tell me what's happening. If this time is a > problem in the pgpool.conf configuration file or if a problem on the > issue of integration of the tools versions. > I wonder if there is any problem with the use of PostgreSQL version > 8.3.9 and 3.0.3 pgPool-II? > I appreciate all the help you can give me. > > This is the pgpool.conf file structure. > > listen_addresses = '*' > port = 5432 > pcp_port = 9898 > socket_dir = '/var/run/postgresql' > pcp_socket_dir = '/var/run/postgresql' > backend_socket_dir = '/var/run/postgresql' > pcp_timeout = 10 > num_init_children = 300 > max_pool = 3 > child_life_time = 300 > connection_life_time = 0 > child_max_connections = 0 > client_idle_limit = 0 > authentication_timeout = 60 > logdir = '/var/run/postgresql' > pid_file_name=%26%2339%3B%2Fvar%2Frun%2Fpgpool%2Fpgpool%2Epid%26%2339%3B > replication_mode = true > load_balance_mode = true > replication_stop_on_mismatch = true > failover_if_affected_tuples_mismatch = false > replicate_select = false > reset_query_list = 'ABORT; DISCARD ALL' > white_function_list = '' > black_function_list = 'nextval,setval' > print_timestamp = true > master_slave_mode = false > delay_threshold = 0 > log_standby_delay = 'none' > connection_cache = true > health_check_timeout = 20 > health_check_period = 0 > health_check_user = 'pgpool2' > #failover_command = '/var/lib/pgsql/data/pgpool-failover %d %h %p %D %m %M' > failover_command = '' > #failback_command = '/var/lib/pgsql/data/pgpool-failback %d %h %p %D %m %M' > failback_command = '' > fail_over_on_backend_error = true > insert_lock = false > ignore_leading_white_space = true > log_statement = false > log_per_node_statement = false > log_connections = true > log_hostname=false > parallel_mode = false > enable_query_cache = false > pgpool2_hostname=%26%2339%3Bbalanceador03%26%2339%3B > system_db_hostname=%26%2339%3Blocalhost%26%2339%3B > system_db_port = 5432 > system_db_dbname=%26%2339%3Bpgpool%26%2339%3B > system_db_schema = 'pgpool_catalog' > system_db_user = 'pgpool' > system_db_password = '' > backend_hostname0 = '15.120.190.12' > backend_port0 = 5432 > backend_weight0 = 1 > backend_data_directory0 = '/var/lib/pgsql/data/' > backend_hostname1 = '15.120.190.11' > backend_port1 = 5432 > backend_weight1 = 1 > backend_data_directory1 = '/var/lib/pgsql/data/' > enable_pool_hba = true > recovery_user = 'pgpool2' > recovery_password = '' > recovery_1st_stage_command = 'base-backup' > #recovery_1st_stage_command = '' > recovery_2nd_stage_command = 'pgpool-recovery-pitr' > #recovery_2nd_stage_command = '' > recovery_timeout = 300 > client_idle_limit_in_recovery = 0 > lobj_lock_table = '' > ssl = false > debug_level = 0 > > > Mary > _______________________________________________ > 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