Re: testing pgpool

Is postgres actually running? And is your pg_hba.conf file configured
to allow local UNIX socket connections?

-tfo

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005

On Mar 16, 2005, at 10:50 AM, ESPARZA JUAREZ EDUARDO wrote:

> Hi list!!
>
>  
>
> I tested pgpool with pgpool.conf as follows:
>
>  
>
> listen_addresses = 'localhost'
>
> port = 9999
>
> socket_dir = '/tmp'
>
> backend_host_name = ''
>
> backend_port = 5432
>
> backend_socket_dir = '/tmp'
>
> secondary_backend_host_name = ''
>
> secondary_backend_port = 0
>
> num_init_children = 15
>
> max_pool = 10
>
> child_life_time = 300
>
> connection_life_time = 0
>
> logdir = '/tmp'
>
> replication_mode = false
>
> replication_strict = true
>
> replication_timeout = 5000
>
> load_balance_mode = false
>
> weight_master = 0.5
>
> weight_secondary = 0.5
>
> replication_stop_on_mismatch = 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 = 0
>
> health_check_user = 'nobody'
>
>  
> but when I try get internal status of pgpool (psql -p 9999 -c 'show
> pool_status' template1) I get:
>  
> psql: could not connect to server: ¸W(at)$g@¹#(at)xöÿ¿Q
> Is the server running locally and accepting
>         connections on Unix domain socket "/tmp/.s.PGSQL.9999"?
>  
> Thank’s
> Eej-