Reinstalei e configurei novamente..
e no primeiro teste consegui acessar..
mas ao acessar diretamente o slave, não encontrei o pgpool conectado a ele..
retornando ao pgpool.conf notei q nao havia alterado a configuração
master_slave_mode para ON
#------------------------------------------------------------------------------
# MASTER/SLAVE MODE
#------------------------------------------------------------------------------
master_slave_mode = on
# Activate master/slave mode
# (change requires restart)
master_slave_sub_mode = 'stream'
# Master/slave sub mode
# Valid values are combinations slony or
# stream. Default is slony.
# (change requires restart)
Após alterar isto, quando tento conectar via pgpool não há retorno..
$ postgres@server1:~$ psql -p 5433 -h 192.168.1.82
$ psql: postgres@server1:~$
Segue o log do pgpool..
2012-04-19 11:44:19 DEBUG: pid 2622: key: listen_addresses
2012-04-19 11:44:19 DEBUG: pid 2622: value: '*' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: port
2012-04-19 11:44:19 DEBUG: pid 2622: value: 5433 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: socket_dir
2012-04-19 11:44:19 DEBUG: pid 2622: value: '/var/run/postgresql' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: pcp_port
2012-04-19 11:44:19 DEBUG: pid 2622: value: 9898 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: pcp_socket_dir
2012-04-19 11:44:19 DEBUG: pid 2622: value: '/var/run/postgresql' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_hostname0
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'server1' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_port0
2012-04-19 11:44:19 DEBUG: pid 2622: value: 5432 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: port slot number 0
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_weight0
2012-04-19 11:44:19 DEBUG: pid 2622: value: 1 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: weight slot number 0 weight:
1.000000
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_data_directory0
2012-04-19 11:44:19 DEBUG: pid 2622: value: '/var/lib/postgresql/9.1/main'
kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_flag0
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'ALLOW_TO_FAILOVER' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: extract_string_tokens: token:
ALLOW_TO_FAILOVER
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: allow_to_failover on
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: slot number 0 flag: 0000
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_hostname1
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'server2' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_port1
2012-04-19 11:44:19 DEBUG: pid 2622: value: 5432 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: port slot number 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_weight1
2012-04-19 11:44:19 DEBUG: pid 2622: value: 1 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: weight slot number 1 weight:
1.000000
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_data_directory1
2012-04-19 11:44:19 DEBUG: pid 2622: value: '/var/lib/postgresql/9.1/main'
kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: backend_flag1
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'ALLOW_TO_FAILOVER' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: extract_string_tokens: token:
ALLOW_TO_FAILOVER
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: allow_to_failover on
2012-04-19 11:44:19 DEBUG: pid 2622: pool_config: slot number 1 flag: 0000
2012-04-19 11:44:19 DEBUG: pid 2622: key: enable_pool_hba
2012-04-19 11:44:19 DEBUG: pid 2622: value: off kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: authentication_timeout
2012-04-19 11:44:19 DEBUG: pid 2622: value: 60 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: ssl
2012-04-19 11:44:19 DEBUG: pid 2622: value: off kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: num_init_children
2012-04-19 11:44:19 DEBUG: pid 2622: value: 32 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: max_pool
2012-04-19 11:44:19 DEBUG: pid 2622: value: 4 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: child_life_time
2012-04-19 11:44:19 DEBUG: pid 2622: value: 300 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: child_max_connections
2012-04-19 11:44:19 DEBUG: pid 2622: value: 0 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: connection_life_time
2012-04-19 11:44:19 DEBUG: pid 2622: value: 0 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: client_idle_limit
2012-04-19 11:44:19 DEBUG: pid 2622: value: 0 kind: 2
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_destination
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'stderr' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: print_timestamp
2012-04-19 11:44:19 DEBUG: pid 2622: value: on kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_connections
2012-04-19 11:44:19 DEBUG: pid 2622: value: on kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_hostname
2012-04-19 11:44:19 DEBUG: pid 2622: value: off kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_statement
2012-04-19 11:44:19 DEBUG: pid 2622: value: on kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_per_node_statement
2012-04-19 11:44:19 DEBUG: pid 2622: value: off kind: 1
2012-04-19 11:44:19 DEBUG: pid 2622: key: log_standby_delay
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'none' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: syslog_facility
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'LOCAL0' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: syslog_ident
2012-04-19 11:44:19 DEBUG: pid 2622: value: 'pgpool' kind: 4
2012-04-19 11:44:19 DEBUG: pid 2622: key: debug_level
2012-04-19 11:44:19 DEBUG: pid 2622: value: 0 kind: 2
pid file found. is another pgpool(2554) is running?
esta ultima linha o log.. perguntado se tenho outro pgpool rodando.. é comum?
Att,
Tulio
>________________________________
> De: Flavio Henrique Araque Gurgel <[email protected]>
>Para: [email protected]
>Enviadas: Quarta-feira, 18 de Abril de 2012 22:17
>Assunto: Re: [pgbr-geral] Failover - Pgpool II + Hot Standby + Stream
>Replication
>
>On 18-04-2012 13:05, Tulio Santos wrote:
>> Boa tarde,
>>
>> Tentei utilizar estes parametros (corrigindo endereços e nomes) na
>> simulação que estou criando..
>> mas não obtive resultado..
>>
>> Ao checar o log do Postgres encontrei.. "EOF inesperado durante conexão
>> do cliente"
>>
>> Alguem imagina o que pode ser?
>
>Se o PostgreSQL estiver em Debian, não é nada. Só o script de
>gerenciamento de serviços do Debian que faz isso no PostgreSQL, nada demais.
>Também pode ser algum monitorador que você tenha colocado em sua rede
>fazendo telnet na porta do PostgreSQL pra saber se ele está vivo.
>
>Sobre o resultado, o que você obteve? Poderia passar o log do pgpool e
>nos explicar qual comportamento ocorreu?
>
>[]s
>
>Flavio Henrique A. Gurgel
>Consultor e Instrutor 4Linux
>Tel: +55-11-2125-4747
>www.4linux.com.br
>_______________________________________________
>pgbr-geral mailing list
>[email protected]
>https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
>
>
>
_______________________________________________
pgbr-geral mailing list
[email protected]
https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
