Re: problemas con pgpool-II

Buenas:

Estoy aprendiendo todavía, pero hoy en pruebas me ha pasado algo parecido.
Lo he solucionado borrando el fichero pgpool_status. En mi caso la ruta era
/var/run/postgresql/pgpool_status.

Mi teoría, no pasa de ser eso, es que alguna vez el pgpool se paro de forma
inesperada y el fichero se quedo allí.

Un saludo.

El 4 de agosto de 2010 14:55, Diego Ayala <netdiego81(at)gmail(dot)com> escribió:

> Buenos dias listeros, quisiera consultarles si alguno tuvo algun problema
> parecido al mio, y si lo pudo solucionar, tengo 2 server, conectados
> mediante pgpool-II, en el cual la replicacion funcionaba de ambos lados, es
> decir, de A a B y de B a A, pero desde hace unos dias, la replicacion de A a
> B no funciona, levanta el pgpool, inicia sin errores, pero mediante el debug
> pude visualizar este mensaje:
> pgpool-II successfully started. version 2.3.3 (tomiteboshi)
> 2010-08-04 08:49:31 DEBUG: pid 19287: I am PCP 19287
> 2010-08-04 08:49:39 DEBUG: pid 19282: I am 19282 accept fd 5
> 2010-08-04 08:49:39 LOG: pid 19282: connection received: host=[local]
> 2010-08-04 08:49:39 DEBUG: pid 19282: Protocol Major: 3 Minor: 0 database:
> postgres user: postgres
> 2010-08-04 08:49:39 DEBUG: pid 19282: new_connection: connecting 0 backend
> 2010-08-04 08:49:39 DEBUG: pid 19282: new_connection: connecting 1 backend
>
> 2010-08-04 08:49:39 DEBUG: pid 19282: new_connection: skipping slot 1
> because backend_status = 3
>
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_ssl: SSL requested but SSL
> support is not available
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length: slot: 0
> length: 8
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 27
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: client_encoding
> value: LATIN1
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 23
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: DateStyle value:
> ISO, DMY
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 25
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: integer_datetimes
> value: on
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 27
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: IntervalStyle
> value: postgres
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 20
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: is_superuser
> value: on
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 27
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: server_encoding
> value: LATIN1
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 25
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: server_version
> value: 8.4.1
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 35
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name:
> session_authorization value: postgres
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 36
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name:
> standard_conforming_strings value: off
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length2: master
> slot: 0 length: 30
> 2010-08-04 08:49:39 DEBUG: pid 19282: 0 th backend: name: TimeZone value:
> America/Asuncion
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length: slot: 0
> length: 12
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_send_auth_ok: send pid 19290 to
> frontend
> 2010-08-04 08:49:39 DEBUG: pid 19282: select_load_balancing_node: selected
> backend id is 0
> 2010-08-04 08:49:39 DEBUG: pid 19282: read_kind_from_backend: read kind
> from 0 th backend Z NUM_BACKENDS: 2
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_process_query: kind from
> backend: Z
> 2010-08-04 08:49:39 DEBUG: pid 19282: pool_read_message_length: slot: 0
> length: 5
> 2010-08-04 08:49:39 DEBUG: pid 19282: ReadyForQuery: message length: 5
> 2010-08-04 08:49:39 DEBUG: pid 19282: ReadyForQuery: transaction state: I
>
> new_connection: skipping slot 1 because backend_status = 3 Haciendo el
> proceso a la inversa, del server B a A, no me sale ese mensaje, y la
> replicacion funciona perfectamente, alguien sabe a que podria deberse eso,
> ya revise todas las configuraciones del pgpool.cong, pg_hba.conf, compare
> con la del server B y no hay diferencias..
>
> Les agradeceria su ayuda.
>