Re: [Pgpool-general] About pgpool-HA
Haruka, thank you very much for the answer, I have installed pgpool-HA like this and the error was solved: ./configure --prefix=/opt/pgpool PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin:/opt/pgpool/bin But I have some questions to you: 1. I can copy and paste the cib.xml present in the documentation of pgpool-HA to cib.xml? 2. I only need to change the nodes ip addres, the virtial IP, and the pgpool parameters like pcp.conf, pgpool.conf and others? 3. If I want to add another nvpair tag to attributes tag, is necessary and specific id? For instance, for adding the options key, what is the id that I need?? Regards. -Mensaje original- De: TAKATSUKA Haruka [mailto:haru...@sra.co.jp] Enviado el: viernes, 25 de noviembre de 2011 03:54 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; tan...@sraoss.co.jp; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA Hi. On Thu, 24 Nov 2011 10:45:02 -0430 Lazaro Rubén García Martinez wrote: > When a try to install Pgpool-HA this errors are shows: > > > [root@PG_01 pgpoolha-734e209]# ./configure --prefix=/opt/pgpool_ha/ > checking for a BSD-compatible install... /usr/bin/install -c > checking for /usr/lib/ocf/resource.d/heartbeat... yes > checking for psql... /usr/bin/psql > checking for pgpool... ./configure: line 1433: error:: command not found > no > configure: creating ./config.status > config.status: creating src/Makefile > > How I can specify the path where Pgpool-II was installed, in configure > command of pgpool-HA?? Sorry, the pgpool-ha configure script works very limitative. "make install" always installs into "/usr/lib/ocf/resource.d/heartbeat". You can copy "pgpool.monitor" to /some/of/bin directory and copy "pgpool" to OCF heartbeat resources directory. > >> Can Pgpool-HA works with heartbeat-3.0.4? Yes. regards, TAKATSUKA Haruka > I have installed Pgpool-II under /opt/pgpool directory. > > Regards. > > -Mensaje original- > De: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén > García Martinez > Enviado el: jueves, 24 de noviembre de 2011 10:14 > Para: Tatsuo Ishii > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About pgpool-HA > > Thanks, I hope Haruka answer my question. > > Regards. > > -----Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: jueves, 24 de noviembre de 2011 10:11 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About pgpool-HA > > Yes. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] RV: About pgpool-HA
Can Pgpool-HA works with heartbeat-3.0.4? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 23 de noviembre de 2011 07:46 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA > Hello everyone, I have some questions related with pgpool-HA. > > 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? Yes. Please make sure that start pgpool with -D option. > 2. Is there a repository for installing pgpool-HA in CentOS from yum command? I don't know. I know Devrim is responsible for creating Redhat rpm for pgpool, but I'm not sure he has done it for pgpool-HA. > 3. Is there any documentation for configuring an environment with Pgpool-II > and Pgpool-HA? It's included in the source code. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ 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
Re: [Pgpool-general] About pgpool-HA
When a try to install Pgpool-HA this errors are shows: [root@PG_01 pgpoolha-734e209]# ./configure --prefix=/opt/pgpool_ha/ checking for a BSD-compatible install... /usr/bin/install -c checking for /usr/lib/ocf/resource.d/heartbeat... yes checking for psql... /usr/bin/psql checking for pgpool... ./configure: line 1433: error:: command not found no configure: creating ./config.status config.status: creating src/Makefile How I can specify the path where Pgpool-II was installed, in configure command of pgpool-HA?? I have installed Pgpool-II under /opt/pgpool directory. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García Martinez Enviado el: jueves, 24 de noviembre de 2011 10:14 Para: Tatsuo Ishii CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA Thanks, I hope Haruka answer my question. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: jueves, 24 de noviembre de 2011 10:11 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA Yes. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Tatsuo, Is Haruka a member of this email list? > > Regards. > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: jueves, 24 de noviembre de 2011 09:54 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About pgpool-HA > > Not sure. Haruka(maintainer of pgpool-HA) may know. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Can Pgpool-HA works with heartbeat-3.0.4? >> >> Regards. >> >> -Mensaje original- >> De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] >> Enviado el: miércoles, 23 de noviembre de 2011 07:46 >> Para: Lazaro Rubén García Martinez >> CC: pgpool-general@pgfoundry.org >> Asunto: Re: [Pgpool-general] About pgpool-HA >> >>> Hello everyone, I have some questions related with pgpool-HA. >>> >>> 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? >> >> Yes. Please make sure that start pgpool with -D option. >> >>> 2. Is there a repository for installing pgpool-HA in CentOS from yum >>> command? >> >> I don't know. I know Devrim is responsible for creating Redhat rpm for >> pgpool, but I'm not sure he has done it for pgpool-HA. >> >>> 3. Is there any documentation for configuring an environment with Pgpool-II >>> and Pgpool-HA? >> >> It's included in the source code. >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> English: http://www.sraoss.co.jp/index_en.php >> Japanese: http://www.sraoss.co.jp ___ 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
Re: [Pgpool-general] About pgpool-HA
Thanks, I hope Haruka answer my question. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: jueves, 24 de noviembre de 2011 10:11 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA Yes. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Tatsuo, Is Haruka a member of this email list? > > Regards. > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: jueves, 24 de noviembre de 2011 09:54 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About pgpool-HA > > Not sure. Haruka(maintainer of pgpool-HA) may know. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Can Pgpool-HA works with heartbeat-3.0.4? >> >> Regards. >> >> -Mensaje original- >> De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] >> Enviado el: miércoles, 23 de noviembre de 2011 07:46 >> Para: Lazaro Rubén García Martinez >> CC: pgpool-general@pgfoundry.org >> Asunto: Re: [Pgpool-general] About pgpool-HA >> >>> Hello everyone, I have some questions related with pgpool-HA. >>> >>> 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? >> >> Yes. Please make sure that start pgpool with -D option. >> >>> 2. Is there a repository for installing pgpool-HA in CentOS from yum >>> command? >> >> I don't know. I know Devrim is responsible for creating Redhat rpm for >> pgpool, but I'm not sure he has done it for pgpool-HA. >> >>> 3. Is there any documentation for configuring an environment with Pgpool-II >>> and Pgpool-HA? >> >> It's included in the source code. >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> English: http://www.sraoss.co.jp/index_en.php >> Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] About pgpool-HA
Tatsuo, Is Haruka a member of this email list? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: jueves, 24 de noviembre de 2011 09:54 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA Not sure. Haruka(maintainer of pgpool-HA) may know. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Can Pgpool-HA works with heartbeat-3.0.4? > > Regards. > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: miércoles, 23 de noviembre de 2011 07:46 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About pgpool-HA > >> Hello everyone, I have some questions related with pgpool-HA. >> >> 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? > > Yes. Please make sure that start pgpool with -D option. > >> 2. Is there a repository for installing pgpool-HA in CentOS from yum command? > > I don't know. I know Devrim is responsible for creating Redhat rpm for > pgpool, but I'm not sure he has done it for pgpool-HA. > >> 3. Is there any documentation for configuring an environment with Pgpool-II >> and Pgpool-HA? > > It's included in the source code. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] About pgpool-HA
Can Pgpool-HA works with heartbeat-3.0.4? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 23 de noviembre de 2011 07:46 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About pgpool-HA > Hello everyone, I have some questions related with pgpool-HA. > > 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? Yes. Please make sure that start pgpool with -D option. > 2. Is there a repository for installing pgpool-HA in CentOS from yum command? I don't know. I know Devrim is responsible for creating Redhat rpm for pgpool, but I'm not sure he has done it for pgpool-HA. > 3. Is there any documentation for configuring an environment with Pgpool-II > and Pgpool-HA? It's included in the source code. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] About pgpool-HA
Hello everyone, I have some questions related with pgpool-HA. 1. Can I use pgpool-HA with pgpool-II 3.1 in streaming replication mode? 2. Is there a repository for installing pgpool-HA in CentOS from yum command? 3. Is there any documentation for configuring an environment with Pgpool-II and Pgpool-HA? Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Error with SSL Consection
That's great, thank you very much for your help and time. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 23 de noviembre de 2011 11:03 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Error with SSL Consection Looks normal. psql first tried with trust auth. Backend requires md5 auth and pool propagated to psql. psql disconnected connection to pgpool and tried with md5 auth again. This time it was successfull. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > This is the log: > > 2011-11-23 06:20:03 LOG: pid 4504: connection received: host=10.13.4.201 > port=33254 > 2011-11-23 06:20:03 DEBUG: pid 4504: Protocol Major: 1234 Minor: 5679 > database: user: > 2011-11-23 06:20:03 DEBUG: pid 4504: SSLRequest from client > 2011-11-23 06:20:03 DEBUG: pid 4504: read_startup_packet: application_name: > psql > 2011-11-23 06:20:03 DEBUG: pid 4504: Protocol Major: 3 Minor: 0 database: > postgres user: postgres > 2011-11-23 06:20:03 DEBUG: pid 4504: new_connection: connecting 0 backend > 2011-11-23 06:20:03 DEBUG: pid 4504: new_connection: connecting 1 backend > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_ssl: sending client->server SSL > request > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_ssl: client->server SSL response: S > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_ssl: sending client->server SSL > request > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_ssl: client->server SSL response: S > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_read_message_length: slot: 0 > length: 12 > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_read_message_length: slot: 1 > length: 12 > 2011-11-23 06:20:03 DEBUG: pid 4504: pool_do_auth: auth kind:5 > 2011-11-23 06:20:03 DEBUG: pid 4504: trying md5 authentication > 2011-11-23 06:20:03 ERROR: pid 4504: pool_ssl: SSL_read: no SSL error reported > 2011-11-23 06:20:03 ERROR: pid 4504: pool_read: read failed (Success) > 2011-11-23 06:20:03 DEBUG: pid 4504: read_password_packet_password: failed to > read password packet "p" > 2011-11-23 06:20:03 DEBUG: pid 4504: do_md5: read_password_packet failed > 2011-11-23 06:20:03 DEBUG: pid 4504: do_md5failed in slot 0 > 2011-11-23 06:20:05 DEBUG: pid 4504: I am 4504 accept fd 6 > 2011-11-23 06:20:05 LOG: pid 4504: connection received: host=10.13.4.201 > port=33257 > 2011-11-23 06:20:05 DEBUG: pid 4504: Protocol Major: 1234 Minor: 5679 > database: user: > 2011-11-23 06:20:05 DEBUG: pid 4504: SSLRequest from client > 2011-11-23 06:20:05 DEBUG: pid 4504: read_startup_packet: application_name: > psql > 2011-11-23 06:20:05 DEBUG: pid 4504: Protocol Major: 3 Minor: 0 database: > postgres user: postgres > 2011-11-23 06:20:05 DEBUG: pid 4504: new_connection: connecting 0 backend > 2011-11-23 06:20:05 DEBUG: pid 4504: new_connection: connecting 1 backend > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_ssl: sending client->server SSL > request > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_ssl: client->server SSL response: S > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_ssl: sending client->server SSL > request > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_ssl: client->server SSL response: S > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 0 > length: 12 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 1 > length: 12 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_do_auth: auth kind:5 > 2011-11-23 06:20:05 DEBUG: pid 4504: trying md5 authentication > 2011-11-23 06:20:05 DEBUG: pid 4504: DB node id: 0 salt: 93aed894 > 2011-11-23 06:20:05 DEBUG: pid 4504: trying md5 authentication > 2011-11-23 06:20:05 DEBUG: pid 4504: DB node id: 1 salt: e2c21f77 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 0 length: 26 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 1 length: 26 > 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: application_name > value: psql > 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: application_name > value: psql > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 0 length: 25 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 1 length: 25 > 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: client_encoding > value: UTF8 > 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: client_encoding > value: UTF8 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 0 length: 23 > 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: > 1 length: 23 > 2011-11-23 06:
Re: [Pgpool-general] Error with SSL Consection
20 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: is_superuser value: on 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: is_superuser value: on 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 0 length: 25 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 1 length: 25 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: server_encoding value: UTF8 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: server_encoding value: UTF8 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 0 length: 25 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 1 length: 25 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: server_version value: 9.0.5 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: server_version value: 9.0.5 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 0 length: 35 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 1 length: 35 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: session_authorization value: postgres 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: session_authorization value: postgres 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 0 length: 36 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 1 length: 36 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: standard_conforming_strings value: off 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: standard_conforming_strings value: off 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 0 length: 29 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length2: master slot: 1 length: 29 2011-11-23 06:20:05 DEBUG: pid 4504: 0 th backend: name: TimeZone value: America/Caracas 2011-11-23 06:20:05 DEBUG: pid 4504: 1 th backend: name: TimeZone value: America/Caracas 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 0 length: 12 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 1 length: 12 2011-11-23 06:20:05 DEBUG: pid 4504: pool_do_auth: cp->info[i]:0xb783f000 pid:4515 2011-11-23 06:20:05 DEBUG: pid 4504: pool_do_auth: cp->info[i]:0xb783f084 pid:32236 2011-11-23 06:20:05 DEBUG: pid 4504: pool_send_auth_ok: send pid 32236 to frontend 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_query_in_progress: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_command_success: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_writing_transaction: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_failed_transaction: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_transaction_isolation: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_skip_reading_from_backends: done 2011-11-23 06:20:05 DEBUG: pid 4504: pool_unset_ignore_till_sync: done 2011-11-23 06:20:05 DEBUG: pid 4504: read_kind_from_backend: read kind from 0 th backend Z NUM_BACKENDS: 2 2011-11-23 06:20:05 DEBUG: pid 4504: read_kind_from_backend: read kind from 1 th backend Z NUM_BACKENDS: 2 2011-11-23 06:20:05 DEBUG: pid 4504: ProcessBackendResponse: kind from backend: Z 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 0 length: 5 2011-11-23 06:20:05 DEBUG: pid 4504: pool_read_message_length: slot: 1 length: 5 2011-11-23 06:20:05 DEBUG: pid 4504: ReadyForQuery: transaction state: Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 23 de noviembre de 2011 10:18 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Error with SSL Consection Could you show logs after this: 2011-11-23 04:37:25 ERROR: pid 17472: pool_read: read failed (Success) -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Tatsuo, thank you very much for your answer, the problem was solved and now I > can connect through SSL: > > In the command window i can see that: > > psql -U desarrollo -h 10.13.4.201 -p -d postgres > Contraseña para usuario desarrollo: > psql (9.0.5) > conexión SSL (cifrado: AES256-SHA, bits: 256) > Digite «help» para obtener ayuda. > > However in the pgpool log these errors are shown, although the connection was > succesful, there are some errors in pgpool log file. > The log says that the connection was established without problem, but the > debug message are matched to ERROR label. Would this a possible bug? > > 2011-11-23 04:37:25 LOG: pid 17472: connection received: host=10.13.4.201 > port=47519 > 2011-11-23 04:37:25 DEBUG: pid 17472: Protocol Major: 1234 Minor: 5679 > database: user: > 2011-11-23 04:37:25 DEBUG: pid 17472: SSLRequest from client > 2011-11-23 04:37:25 DEBUG: pid 17472: read_startup_packet: application_name: > psql > 2011-11-23 04
Re: [Pgpool-general] Error with SSL Consection
Tatsuo, thank you very much for your answer, the problem was solved and now I can connect through SSL: In the command window i can see that: psql -U desarrollo -h 10.13.4.201 -p -d postgres Contraseña para usuario desarrollo: psql (9.0.5) conexión SSL (cifrado: AES256-SHA, bits: 256) Digite «help» para obtener ayuda. However in the pgpool log these errors are shown, although the connection was succesful, there are some errors in pgpool log file. The log says that the connection was established without problem, but the debug message are matched to ERROR label. Would this a possible bug? 2011-11-23 04:37:25 LOG: pid 17472: connection received: host=10.13.4.201 port=47519 2011-11-23 04:37:25 DEBUG: pid 17472: Protocol Major: 1234 Minor: 5679 database: user: 2011-11-23 04:37:25 DEBUG: pid 17472: SSLRequest from client 2011-11-23 04:37:25 DEBUG: pid 17472: read_startup_packet: application_name: psql 2011-11-23 04:37:25 DEBUG: pid 17472: Protocol Major: 3 Minor: 0 database: postgres user: desarrollo 2011-11-23 04:37:25 DEBUG: pid 17472: new_connection: connecting 0 backend 2011-11-23 04:37:25 DEBUG: pid 17472: new_connection: connecting 1 backend 2011-11-23 04:37:25 DEBUG: pid 17472: pool_ssl: sending client->server SSL request 2011-11-23 04:37:25 DEBUG: pid 17472: pool_ssl: client->server SSL response: S 2011-11-23 04:37:25 DEBUG: pid 17472: pool_ssl: sending client->server SSL request 2011-11-23 04:37:25 DEBUG: pid 17472: pool_ssl: client->server SSL response: S 2011-11-23 04:37:25 DEBUG: pid 17472: pool_read_message_length: slot: 0 length: 12 2011-11-23 04:37:25 DEBUG: pid 17472: pool_read_message_length: slot: 1 length: 12 2011-11-23 04:37:25 DEBUG: pid 17472: pool_do_auth: auth kind:5 2011-11-23 04:37:25 DEBUG: pid 17472: trying md5 authentication 2011-11-23 04:37:25 ERROR: pid 17472: pool_ssl: SSL_read: no SSL error reported 2011-11-23 04:37:25 ERROR: pid 17472: pool_read: read failed (Success) Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 23 de noviembre de 2011 04:21 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Error with SSL Consection Can you try like this? 1) configure num_init_children to 1. 2) restart pgpool 3) find pgpool child process pid(hint: ps status is "pgpool: wait for connection request") 4) strace -p the_pid 5) connect to pgpool strace should show where pgpool tried to find ssl cert file. Make sure that it is /opt/pgpool/ssl/server.cert. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hello everyone in the list, I am proving the connecting SSL through with > Pgpool, the pgpool configuration parameters related with SSL are: > > # - SSL Connections - > > ssl = on > ssl_key = '/opt/pgpool/ssl/server.key' > ssl_cert = '/opt/pgpool/ssl/server.cert' > #ssl_ca_cert = '' > #ssl_ca_cert_dir = '' > > But in pgpool.log file i see this error: > > 2011-11-22 06:42:02 LOG: pid 14011: connection received: host=10.13.4.201 > port=40434 > 2011-11-22 06:42:02 DEBUG: pid 14011: Protocol Major: 1234 Minor: 5679 > database: user: > 2011-11-22 06:42:02 DEBUG: pid 14011: SSLRequest from client > 2011-11-22 06:42:02 ERROR: pid 14011: pool_ssl: Loading SSL certificate: No > such file or directory > > Nevertheless I can connect to postgreSQL through Pgpool. > > Please can anybody tell me, What could be the reason for this error? > > I am using Pgpool-II V_3.1_stable with PostgreSQL 9.0.5. > > Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Error with SSL Consection
Hello everyone in the list, I am proving the connecting SSL through with Pgpool, the pgpool configuration parameters related with SSL are: # - SSL Connections - ssl = on ssl_key = '/opt/pgpool/ssl/server.key' ssl_cert = '/opt/pgpool/ssl/server.cert' #ssl_ca_cert = '' #ssl_ca_cert_dir = '' But in pgpool.log file i see this error: 2011-11-22 06:42:02 LOG: pid 14011: connection received: host=10.13.4.201 port=40434 2011-11-22 06:42:02 DEBUG: pid 14011: Protocol Major: 1234 Minor: 5679 database: user: 2011-11-22 06:42:02 DEBUG: pid 14011: SSLRequest from client 2011-11-22 06:42:02 ERROR: pid 14011: pool_ssl: Loading SSL certificate: No such file or directory Nevertheless I can connect to postgreSQL through Pgpool. Please can anybody tell me, What could be the reason for this error? I am using Pgpool-II V_3.1_stable with PostgreSQL 9.0.5. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Tatsuo, thank you very much for the answer. I only have one question: Is there any estimated date for release PGPool-II 3.2? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: lunes, 21 de noviembre de 2011 09:24 Para: Lazaro Rubén García Martinez CC: guilla...@lelarge.info; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password I have checked pgpool-II 3.1 code and found that my explanation was wrong. 1) sr_check_user and sr_check_password are working fine with 3.1 even with md5 auth. 2) health_check_password is ignored in 3.1. So you can not use other trust with health_check_user. For #2, it seems a fix to recognize health_check_password will break backward compatibility. Because 3.1 code uses V2 protocol (used by 7.3 or before). To enable md5 auth, I need to replace it by using make_persistent_db_connection(), which handles V3 protocol only. So it seems there's no hope to recognize health_check_password in 3.1.x. 3.2 will allow to use md5 auth with health_check_password for price of discontinuing support for V2 protocol. BTW, problem with SSL is totally different story. It seems someone forgot to allow to use SSL with health checking and make_persistent_db_connection()... -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > I configured pg_hba.conf like this: > > #For recovery_user and health_check_user of pgpool > hostssl postgrespgpool 10.13.4.201/32 > md5 > hostssl template1 pgpool 10.13.4.201/32 > md5 > > #For sr_check_user of pgpool > hostssl postgressr_pgpool 10.13.4.201/32 > trust > hostssl template1 sr_pgpool 10.13.4.201/32 > trust > > The postgresql log file shows this error: > > LOG: connection received: host=10.13.4.201 port=50640 > LOG: could not receive data from client: Connection reset by peer > > The pgpoolAdmin tool doesn't shows the information about master and standby > nodes. > > Please, I need configure the access from pgpool to postgreSQL through md5 > authentication method, or other authentication method different of trust. > > Is this possible with Pgpool-II??, because I tested it, in different ways and > always these errors are shown. > > pgpool.conf is configure like this: > > * > ssl = on > ssl_key = '/opt/pgpool/ssl/server.key' > ssl_cert = '/opt/pgpool/ssl/server.cert' > > sr_check_user = 'sr_pgpool' > sr_check_password = '' > > health_check_user = 'pgpool' > health_check_password = 'pgpool' > > recovery_user = 'pgpool' > recovery_password = 'pgpool' > > ************ > > Regards and thank you very much for your time. > > -Mensaje original- > De: Lazaro Rubén García Martinez > Enviado el: lunes, 21 de noviembre de 2011 10:59 > Para: Lazaro Rubén García Martinez; Guillaume Lelarge > CC: pgpool-general@pgfoundry.org > Asunto: RE: [Pgpool-general] Authentication method used for > sr_check_password, health_check_password and recovery_password > > Continuing with this thread, I have some doubt about using SSL connections > with pgpool and postgreSQL, my pg_hba.conf have this configuration at this > moment: > > hostssl postgrespgpool 10.13.4.201/32 > trust > hostssl template1 pgpool 10.13.4.201/32 > trust > hostssl postgressr_pgpool 10.13.4.201/32 > trust > hostssl template1 sr_pgpool 10.13.4.201/32 > trust > > But in the postgreSQL log file, this error is shows: > > LOG: connection received: host=10.13.4.201 port=50423 > LOG: connection received: host=10.13.4.201 port=50424 > LOG: connection authorized: user=sr_pgpool database=postgres > LOG: connection authorized: user=sr_pgpool database=postgres > LOG: statement: SELECT pg_is_in_recovery() > LOG: statement: SELECT pg_current_xlog_location() > LOG: disconnection: session time: 0:00:00.092 user=sr_pgpool > database=postgres host=10.13.4.201 port=50424 > LOG: disconnection: session time: 0:00:00.096 user=sr_pgpool > database=postgres host=10.13.4.201 port=5042
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
I configured pg_hba.conf like this: #For recovery_user and health_check_user of pgpool hostssl postgrespgpool 10.13.4.201/32 md5 hostssl template1 pgpool 10.13.4.201/32 md5 #For sr_check_user of pgpool hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust The postgresql log file shows this error: LOG: connection received: host=10.13.4.201 port=50640 LOG: could not receive data from client: Connection reset by peer The pgpoolAdmin tool doesn't shows the information about master and standby nodes. Please, I need configure the access from pgpool to postgreSQL through md5 authentication method, or other authentication method different of trust. Is this possible with Pgpool-II??, because I tested it, in different ways and always these errors are shown. pgpool.conf is configure like this: * ssl = on ssl_key = '/opt/pgpool/ssl/server.key' ssl_cert = '/opt/pgpool/ssl/server.cert' sr_check_user = 'sr_pgpool' sr_check_password = '' health_check_user = 'pgpool' health_check_password = 'pgpool' recovery_user = 'pgpool' recovery_password = 'pgpool' Regards and thank you very much for your time. -Mensaje original- De: Lazaro Rubén García Martinez Enviado el: lunes, 21 de noviembre de 2011 10:59 Para: Lazaro Rubén García Martinez; Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password Continuing with this thread, I have some doubt about using SSL connections with pgpool and postgreSQL, my pg_hba.conf have this configuration at this moment: hostssl postgrespgpool 10.13.4.201/32 trust hostssl template1 pgpool 10.13.4.201/32 trust hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust But in the postgreSQL log file, this error is shows: LOG: connection received: host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50424 LOG: connection authorized: user=sr_pgpool database=postgres LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: statement: SELECT pg_current_xlog_location() LOG: disconnection: session time: 0:00:00.092 user=sr_pgpool database=postgres host=10.13.4.201 port=50424 LOG: disconnection: session time: 0:00:00.096 user=sr_pgpool database=postgres host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50426 FATAL: no pg_hba.conf entry for host "10.13.4.201", user "pgpool", database "postgres", SSL off LOG: connection received: host=10.13.4.201 port=50428 LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.048 user=sr_pgpool database=postgres host=10.13.4.201 port=50428 LOG: connection received: host=10.13.4.201 port=50432 LOG: connection authorized: user=pgpool database=template1 LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.053 user=pgpool database=template1 host=10.13.4.201 port=50432 Why pgpool can connect to the database template1, and not to postgres database? In what case pgpool connects to database postgres and in what case connects to template1 database? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García Martinez Enviado el: domingo, 20 de noviembre de 2011 06:43 Para: Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password I am agree with you, but if it is not a bug, what is the purpose for having sr_sheck_password property in pgpool.conf file?. I think this property can confuse pgpool's users, for this reason I propose -1. If you understand that this feature should be present in Pgpool 3.2, I will agree with you too. Regards. ________ De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 17:58 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_che
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Continuing with this thread, I have some doubt about using SSL connections with pgpool and postgreSQL, my pg_hba.conf have this configuration at this moment: hostssl postgrespgpool 10.13.4.201/32 trust hostssl template1 pgpool 10.13.4.201/32 trust hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust But in the postgreSQL log file, this error is shows: LOG: connection received: host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50424 LOG: connection authorized: user=sr_pgpool database=postgres LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: statement: SELECT pg_current_xlog_location() LOG: disconnection: session time: 0:00:00.092 user=sr_pgpool database=postgres host=10.13.4.201 port=50424 LOG: disconnection: session time: 0:00:00.096 user=sr_pgpool database=postgres host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50426 FATAL: no pg_hba.conf entry for host "10.13.4.201", user "pgpool", database "postgres", SSL off LOG: connection received: host=10.13.4.201 port=50428 LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.048 user=sr_pgpool database=postgres host=10.13.4.201 port=50428 LOG: connection received: host=10.13.4.201 port=50432 LOG: connection authorized: user=pgpool database=template1 LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.053 user=pgpool database=template1 host=10.13.4.201 port=50432 Why pgpool can connect to the database template1, and not to postgres database? In what case pgpool connects to database postgres and in what case connects to template1 database? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García Martinez Enviado el: domingo, 20 de noviembre de 2011 06:43 Para: Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password I am agree with you, but if it is not a bug, what is the purpose for having sr_sheck_password property in pgpool.conf file?. I think this property can confuse pgpool's users, for this reason I propose -1. If you understand that this feature should be present in Pgpool 3.2, I will agree with you too. Regards. De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 17:58 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password On Sun, 2011-11-20 at 17:24 -0430, Lazaro Rubén García Martinez wrote: > I think this feature is very important, because having trust acces in > pg_hba.conf is not a good idea. I understand that and I agree with you. The problem is not on the feature itself, but on which release it should be delivered. If the feature is really urgent to get out there, then we should release 3.2 quickly. We shouldn't put it in 3.1.whatever because 3.1.whatever could get out before 3.2. Minor releases shouldn't change behaviour apart from bugfixes. That's an important part of the trust you can have in a software. If we start to add features on bugfix releases, many people will stop doing minor updates on pgpool, afraid of bugs which might be included with new features. I know I'll do if this will happen, and I won't encourage my customers to upgrade their pgpool. So, definite +1 to add this feature to pgpool, +1 to add it to 3.2, -1 to add it as a bugfix in 3.1.1. It definitely is not a bugfix. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ 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
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
I configured pg_hba.conf like this: #For recovery_user and health_check_user of pgpool hostssl postgrespgpool 10.13.4.201/32 md5 hostssl template1 pgpool 10.13.4.201/32 md5 #For sr_check_user of pgpool hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust The postgresql log file shows this error: LOG: connection received: host=10.13.4.201 port=50640 LOG: could not receive data from client: Connection reset by peer The pgpoolAdmin tool doesn't shows the information about master and standby nodes. Please, I need configure the access from pgpool to postgreSQL through md5 authentication method, or other authentication method different of trust. Is this possible with Pgpool-II??, because I tested it, in different ways and always these errors are shown. pgpool.conf is configure like this: * ssl = on ssl_key = '/opt/pgpool/ssl/server.key' ssl_cert = '/opt/pgpool/ssl/server.cert' sr_check_user = 'sr_pgpool' sr_check_password = '' health_check_user = 'pgpool' health_check_password = 'pgpool' recovery_user = 'pgpool' recovery_password = 'pgpool' Regards and thank you very much for your time. -Mensaje original- De: Lazaro Rubén García Martinez Enviado el: lunes, 21 de noviembre de 2011 10:59 Para: Lazaro Rubén García Martinez; Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password Continuing with this thread, I have some doubt about using SSL connections with pgpool and postgreSQL, my pg_hba.conf have this configuration at this moment: hostssl postgrespgpool 10.13.4.201/32 trust hostssl template1 pgpool 10.13.4.201/32 trust hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust But in the postgreSQL log file, this error is shows: LOG: connection received: host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50424 LOG: connection authorized: user=sr_pgpool database=postgres LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: statement: SELECT pg_current_xlog_location() LOG: disconnection: session time: 0:00:00.092 user=sr_pgpool database=postgres host=10.13.4.201 port=50424 LOG: disconnection: session time: 0:00:00.096 user=sr_pgpool database=postgres host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50426 FATAL: no pg_hba.conf entry for host "10.13.4.201", user "pgpool", database "postgres", SSL off LOG: connection received: host=10.13.4.201 port=50428 LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.048 user=sr_pgpool database=postgres host=10.13.4.201 port=50428 LOG: connection received: host=10.13.4.201 port=50432 LOG: connection authorized: user=pgpool database=template1 LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.053 user=pgpool database=template1 host=10.13.4.201 port=50432 Why pgpool can connect to the database template1, and not to postgres database? In what case pgpool connects to database postgres and in what case connects to template1 database? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García Martinez Enviado el: domingo, 20 de noviembre de 2011 06:43 Para: Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password I am agree with you, but if it is not a bug, what is the purpose for having sr_sheck_password property in pgpool.conf file?. I think this property can confuse pgpool's users, for this reason I propose -1. If you understand that this feature should be present in Pgpool 3.2, I will agree with you too. Regards. ________ De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 17:58 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_che
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Continuing with this thread, I have some doubt about using SSL connections with pgpool and postgreSQL, my pg_hba.conf have this configuration at this moment: hostssl postgrespgpool 10.13.4.201/32 trust hostssl template1 pgpool 10.13.4.201/32 trust hostssl postgressr_pgpool 10.13.4.201/32 trust hostssl template1 sr_pgpool 10.13.4.201/32 trust But in the postgreSQL log file, this error is shows: LOG: connection received: host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50424 LOG: connection authorized: user=sr_pgpool database=postgres LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: statement: SELECT pg_current_xlog_location() LOG: disconnection: session time: 0:00:00.092 user=sr_pgpool database=postgres host=10.13.4.201 port=50424 LOG: disconnection: session time: 0:00:00.096 user=sr_pgpool database=postgres host=10.13.4.201 port=50423 LOG: connection received: host=10.13.4.201 port=50426 FATAL: no pg_hba.conf entry for host "10.13.4.201", user "pgpool", database "postgres", SSL off LOG: connection received: host=10.13.4.201 port=50428 LOG: connection authorized: user=sr_pgpool database=postgres LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.048 user=sr_pgpool database=postgres host=10.13.4.201 port=50428 LOG: connection received: host=10.13.4.201 port=50432 LOG: connection authorized: user=pgpool database=template1 LOG: statement: SELECT pg_is_in_recovery() LOG: disconnection: session time: 0:00:00.053 user=pgpool database=template1 host=10.13.4.201 port=50432 Why pgpool can connect to the database template1, and not to postgres database? In what case pgpool connects to database postgres and in what case connects to template1 database? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García Martinez Enviado el: domingo, 20 de noviembre de 2011 06:43 Para: Guillaume Lelarge CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password I am agree with you, but if it is not a bug, what is the purpose for having sr_sheck_password property in pgpool.conf file?. I think this property can confuse pgpool's users, for this reason I propose -1. If you understand that this feature should be present in Pgpool 3.2, I will agree with you too. Regards. De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 17:58 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password On Sun, 2011-11-20 at 17:24 -0430, Lazaro Rubén García Martinez wrote: > I think this feature is very important, because having trust acces in > pg_hba.conf is not a good idea. I understand that and I agree with you. The problem is not on the feature itself, but on which release it should be delivered. If the feature is really urgent to get out there, then we should release 3.2 quickly. We shouldn't put it in 3.1.whatever because 3.1.whatever could get out before 3.2. Minor releases shouldn't change behaviour apart from bugfixes. That's an important part of the trust you can have in a software. If we start to add features on bugfix releases, many people will stop doing minor updates on pgpool, afraid of bugs which might be included with new features. I know I'll do if this will happen, and I won't encourage my customers to upgrade their pgpool. So, definite +1 to add this feature to pgpool, +1 to add it to 3.2, -1 to add it as a bugfix in 3.1.1. It definitely is not a bugfix. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ 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
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
I am agree with you, but if it is not a bug, what is the purpose for having sr_sheck_password property in pgpool.conf file?. I think this property can confuse pgpool's users, for this reason I propose -1. If you understand that this feature should be present in Pgpool 3.2, I will agree with you too. Regards. De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 17:58 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: RE: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password On Sun, 2011-11-20 at 17:24 -0430, Lazaro Rubén García Martinez wrote: > I think this feature is very important, because having trust acces in > pg_hba.conf is not a good idea. I understand that and I agree with you. The problem is not on the feature itself, but on which release it should be delivered. If the feature is really urgent to get out there, then we should release 3.2 quickly. We shouldn't put it in 3.1.whatever because 3.1.whatever could get out before 3.2. Minor releases shouldn't change behaviour apart from bugfixes. That's an important part of the trust you can have in a software. If we start to add features on bugfix releases, many people will stop doing minor updates on pgpool, afraid of bugs which might be included with new features. I know I'll do if this will happen, and I won't encourage my customers to upgrade their pgpool. So, definite +1 to add this feature to pgpool, +1 to add it to 3.2, -1 to add it as a bugfix in 3.1.1. It definitely is not a bugfix. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
I think this feature is very important, because having trust acces in pg_hba.conf is not a good idea. Regards. De: Guillaume Lelarge [guilla...@lelarge.info] Enviado el: domingo, 20 de noviembre de 2011 5:40 Para: Tatsuo Ishii CC: Lazaro Rubén García Martinez; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password On Sun, 2011-11-20 at 18:31 +0900, Tatsuo Ishii wrote: > > On Sun, 2011-11-20 at 08:13 +0900, Tatsuo Ishii wrote: > >> > Thank you very much for the answer. > >> > Is there a plan for using sr_check_password in the next release of > >> > pgpool 3.1 series? > >> > >> Yes, it's in my plan. Unless supporting sr_check_password is too > >> invasive... > > > > Sorry, but I disagree. Either it is a bug and it should get fixed, or it > > isn't a bug, and this new feature should go into 3.2. Changing behaviour > > between minor releases should not happen. > > If sr_check_password is not in 3.1, you are argument is perfectly > adequate. But in 3.1 sr_check_password is there but it's not > used. Doesn't it a bug? Could be a forgotten feature. In that case, I advocate to make it work in 3.1. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Great!!! Regards De: Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: sábado, 19 de noviembre de 2011 18:43 Para: Lazaro Rubén García Martinez CC: is...@sraoss.co.jp; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password > Thank you very much for the answer. > Is there a plan for using sr_check_password in the next release of pgpool 3.1 > series? Yes, it's in my plan. Unless supporting sr_check_password is too invasive... -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Regards. > > De: Tatsuo Ishii [is...@sraoss.co.jp] > Enviado el: sábado, 19 de noviembre de 2011 2:26 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Authentication method used for > sr_check_password, health_check_password and recovery_password > > First, currently sr_check_password is not uused. Leave it as it is. > For health_check_password and recovery_password, you can use whatever > auth method PostgreSQL supports. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Hello everyone in the list, I would like to know what is the authentication >> method that I need to use in pg_hba.conf of Postgresql for configuring >> sr_check_password, health_check_password and recovery_password in >> pgpool.conf?? >> >> Thank you for your attention. >> >> Regards. >> >> >> ___ >> 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
Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Thank you very much for the answer. Is there a plan for using sr_check_password in the next release of pgpool 3.1 series? Regards. De: Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: sábado, 19 de noviembre de 2011 2:26 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password First, currently sr_check_password is not uused. Leave it as it is. For health_check_password and recovery_password, you can use whatever auth method PostgreSQL supports. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hello everyone in the list, I would like to know what is the authentication > method that I need to use in pg_hba.conf of Postgresql for configuring > sr_check_password, health_check_password and recovery_password in > pgpool.conf?? > > Thank you for your attention. > > Regards. > > > ___ > 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
[Pgpool-general] Authentication method used for sr_check_password, health_check_password and recovery_password
Hello everyone in the list, I would like to know what is the authentication method that I need to use in pg_hba.conf of Postgresql for configuring sr_check_password, health_check_password and recovery_password in pgpool.conf?? Thank you for your attention. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem with pgpoolAdmin and pgpool 3.1
Tatsuo, thank you very much for the answer. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: jueves, 10 de noviembre de 2011 11:56 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem with pgpoolAdmin and pgpool 3.1 > Hello everyone in the list, I have a doubt or a problem with pgpool and > pgpoolAdmin V 3.1. > > Firstly: > > I have an user called pgpool in my postgres servers for permorf > sr_check_user, health_check_user and recovery_user by pgpool-II. > > In the one test, pgpool user has trust access in pg_hba.conf of postgresql > like this: > > host all > pgpool 10.13.4.202/32 > trust > > And pgpool.conf is configured like this: > > sr_check_user = 'pgpool' > sr_check_password = '' > > health_check_user = 'pgpool' > health_check_password = '' > > recovery_user = 'pgpool' > recovery_password = '' > > And pgpolAdmin shows this report: > > [cid:image001.jpg@01CC9F37.6E388FC0] > > In the second test: > > pgpool user has md5 access in pg_hba.conf of postgresql like this: > > host all > pgpool 10.13.4.202/32 > md5 > > And pgpool.conf is configured like this: > > sr_check_user = 'pgpool' > sr_check_password = 'pgpool' > > health_check_user = 'pgpool' > health_check_password = 'pgpool' > > recovery_user = 'pgpool' > recovery_password = 'pgpool' > > And pgpolAdmin shows this report: > > [cid:image003.jpg@01CC9F37.6E388FC0] > > Why in the first configuration test, I can see the information about primary > and standby server and in the second test, this information is not shows?? md5 is not allowed for sr_check_user and health_check_user at the moment. Please use trust instead. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Problem with pgpoolAdmin and pgpool 3.1
Hello everyone in the list, I have a doubt or a problem with pgpool and pgpoolAdmin V 3.1. Firstly: I have an user called pgpool in my postgres servers for permorf sr_check_user, health_check_user and recovery_user by pgpool-II. In the one test, pgpool user has trust access in pg_hba.conf of postgresql like this: host all pgpool 10.13.4.202/32 trust And pgpool.conf is configured like this: sr_check_user = 'pgpool' sr_check_password = '' health_check_user = 'pgpool' health_check_password = '' recovery_user = 'pgpool' recovery_password = '' And pgpolAdmin shows this report: [cid:image001.jpg@01CC9F37.6E388FC0] In the second test: pgpool user has md5 access in pg_hba.conf of postgresql like this: host all pgpool 10.13.4.202/32 md5 And pgpool.conf is configured like this: sr_check_user = 'pgpool' sr_check_password = 'pgpool' health_check_user = 'pgpool' health_check_password = 'pgpool' recovery_user = 'pgpool' recovery_password = 'pgpool' And pgpolAdmin shows this report: [cid:image003.jpg@01CC9F37.6E388FC0] Why in the first configuration test, I can see the information about primary and standby server and in the second test, this information is not shows?? Thank you very much everyone for your time. Regards. <><>___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] ppool2 logging
Has the directory for storing pgpool.logs the appropriate permissions and owner?? Try to run pgpool, through the command window. By this way you can see the exactly error causes. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Martín Marqués Enviado el: jueves, 10 de noviembre de 2011 01:20 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] ppool2 logging I can't find what I'm doing wrong, but I can't get pgpool to log. I'm using version from debian testing (updated), and have debug set to 4, but no log file available anywhere. Which are the steps to get pgpool2 logs? -- Martín Marqués select 'martin.marques' || '@' || 'gmail.com' DBA, Programador, Administrador ___ 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
[Pgpool-general] Problem with pgpoolAdmin and pgpool 3.1
Hello everyone in the list, I have a doubt or a problem with pgpool and pgpoolAdmin V 3.1. Firstly: I have an user called pgpool in my postgres servers for permorf sr_check_user, health_check_user and recovery_user by pgpool-II. In the one test, pgpool user has trust access in pg_hba.conf of postgresql like this: host all pgpool 10.13.4.202/32 trust And pgpool.conf is configured like this: sr_check_user = 'pgpool' sr_check_password = '' health_check_user = 'pgpool' health_check_password = '' recovery_user = 'pgpool' recovery_password = '' And pgpolAdmin shows this report: [cid:image001.jpg@01CC9F37.6E388FC0] In the second test: pgpool user has md5 access in pg_hba.conf of postgresql like this: host all pgpool 10.13.4.202/32 md5 And pgpool.conf is configured like this: sr_check_user = 'pgpool' sr_check_password = 'pgpool' health_check_user = 'pgpool' health_check_password = 'pgpool' recovery_user = 'pgpool' recovery_password = 'pgpool' And pgpolAdmin shows this report: [cid:image003.jpg@01CC9F37.6E388FC0] Why in the first configuration test, I can see the information about primary and standby server and in the second test, this information is not shows?? Thank you very much everyone for your time. Regards. <><>___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Should I configure system_db_dbname parameter while running in connection pooling mode?
>My question is, my understanding is that the following parameters are not >applicable/not required to configure while running in connection pooling >mode. Am I correct? Yes >Additionally, it would also be useful, if somebody can >explain the functionality of these parameters and in which mode of pgpool >feature is this required. This parameters are configured if you use parallel mode. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Gnanakumar Enviado el: jueves, 10 de noviembre de 2011 01:42 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] Should I configure system_db_dbname parameter while running in connection pooling mode? Hi, We're running PostgreSQL 8.2.22 and pgpool-II-2.0.1. In our case, pgpool is solely used for connection pooling purpose and we're not using other features of pgpool like replication, load balance, parallel query, etc. My question is, my understanding is that the following parameters are not applicable/not required to configure while running in connection pooling mode. Am I correct? Additionally, it would also be useful, if somebody can explain the functionality of these parameters and in which mode of pgpool feature is this required. # system DB info system_db_hostname = '127.0.0.1' system_db_port = 5432 system_db_dbname = 'pgpool' system_db_schema = 'pgpool_catalog' system_db_user = 'pgpool' system_db_password = '' Is there any pgpool doc/link/resource that lists *only* parameters required to configure (so that I can just ignore/no need to unnecessarily worry about other parameters) pgpool in connection pooling mode? Regards, Gnanam ___ 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
Re: [Pgpool-general] How to download Pgpool-II V3_1_STABLE
Tatsuo and Guillaume, thank you very much for your help, This was what I was looking. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 09 de noviembre de 2011 11:21 Para: Lazaro Rubén García Martinez CC: guilla...@lelarge.info; pgpool-general@pgfoundry.org Asunto: Re: How to download Pgpool-II V3_1_STABLE Probably firewall thing? Alternatively, you can download snapshot of 3.1 stable release from git web interface. Visit: http://git.postgresql.org/gitweb/ Search link named "pgpool2.git" and click. In the bottom of the page, there is a "heads" section. You find "V3.1_STABLE" and click. In the page top line is the latest version of 3.1 stable. Click the right most link "snapshot". http://git.postgresql.org/gitweb/?p=pgpool2.git;a=snapshot;h=8b47d55274ddf66059867cf3eb912a2cd9f932b6;sf=tgz You will get the tar ball. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Thanks for your answer but when I execute > [root@MVprueba ~]# git clone git://git.postgresql.org/git/pgpool2.git > This is shown: > > Initialized empty Git repository in /root/pgpool2/.git/ > git.postgresql.org[0: 204.145.120.222]: errno=Connection timed out > fatal: unable to connect a socket (Connection timed out) > > What I am making wrong? > > Regards. > > -Mensaje original- > De: Guillaume Lelarge [mailto:guilla...@lelarge.info] > Enviado el: miércoles, 09 de noviembre de 2011 03:51 > Para: Lazaro Rubén García Martinez > CC: Tatsuo Ishii; pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] pgpool-II child process is segfaulting > > On Wed, 2011-11-09 at 13:40 -0430, Lazaro Rubén García Martinez wrote: >> Tatsuo, thank you very much for your answer, but when I execute: >> >> cvs -d :pserver:anonym...@cvs.pgfoundry.org:/cvsroot/pgpool login >> >> This error is shown: >> >> cvs [login aborted]: connect to [cvs.pgfoundry.org]:2401 failed: Connection >> timed out >> >> I have access to internet by a proxy there is in my organization, that means >> I have not free access to internet. >> > > It isn't because of your proxy. pgfoundry was unavailable for a few > days. > >> Could you tell me, why is the cause of this problem, or if you have time, >> could you send me V3_1_STABLE to this email address? >> >> lazaro3...@gmail.com >> >> >> Is very important for my download the V3_1_STABLE. >> > > It seems you should be able to download it right now. > > BTW, pgpool moved to git quite recently. So you can grab it from > git.postgresql.org, using: > > git clone git://git.postgresql.org/git/pgpool2.git > > and, then > > git checkout V3_1_STABLE > > > -- > Guillaume > http://blog.guillaume.lelarge.info > http://www.dalibo.com > ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] How to download Pgpool-II V3_1_STABLE
Thanks for your answer but when I execute [root@MVprueba ~]# git clone git://git.postgresql.org/git/pgpool2.git This is shown: Initialized empty Git repository in /root/pgpool2/.git/ git.postgresql.org[0: 204.145.120.222]: errno=Connection timed out fatal: unable to connect a socket (Connection timed out) What I am making wrong? Regards. -Mensaje original- De: Guillaume Lelarge [mailto:guilla...@lelarge.info] Enviado el: miércoles, 09 de noviembre de 2011 03:51 Para: Lazaro Rubén García Martinez CC: Tatsuo Ishii; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] pgpool-II child process is segfaulting On Wed, 2011-11-09 at 13:40 -0430, Lazaro Rubén García Martinez wrote: > Tatsuo, thank you very much for your answer, but when I execute: > > cvs -d :pserver:anonym...@cvs.pgfoundry.org:/cvsroot/pgpool login > > This error is shown: > > cvs [login aborted]: connect to [cvs.pgfoundry.org]:2401 failed: Connection > timed out > > I have access to internet by a proxy there is in my organization, that means > I have not free access to internet. > It isn't because of your proxy. pgfoundry was unavailable for a few days. > Could you tell me, why is the cause of this problem, or if you have time, > could you send me V3_1_STABLE to this email address? > > lazaro3...@gmail.com > > > Is very important for my download the V3_1_STABLE. > It seems you should be able to download it right now. BTW, pgpool moved to git quite recently. So you can grab it from git.postgresql.org, using: git clone git://git.postgresql.org/git/pgpool2.git and, then git checkout V3_1_STABLE -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool-II child process is segfaulting
Tatsuo, thank you very much for your answer, but when I execute: cvs -d :pserver:anonym...@cvs.pgfoundry.org:/cvsroot/pgpool login This error is shown: cvs [login aborted]: connect to [cvs.pgfoundry.org]:2401 failed: Connection timed out I have access to internet by a proxy there is in my organization, that means I have not free access to internet. Could you tell me, why is the cause of this problem, or if you have time, could you send me V3_1_STABLE to this email address? lazaro3...@gmail.com Is very important for my download the V3_1_STABLE. Thank you very much for your time. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: jueves, 27 de octubre de 2011 06:39 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] pgpool-II child process is segfaulting > Hello Tatsuo, How I can download the latest stable release of pgpool-II 3.1, > with the latest modifications developed? 3.1 stable is tagged as "V3_1_STABLE". You can get it from CVS repository by specifiying the tag. See http://pgfoundry.org/scm/?group_id=155 for more details. In the mean time I have sent you the tar ball via private email for just in case. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Regards. > > -Mensaje original- > De: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii > Enviado el: jueves, 27 de octubre de 2011 07:56 > Para: ronny.wink...@communardo.de > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] pgpool-II child process is segfaulting > > Can you try CVS HEAD? > > After 3.1 released, I have committed some fixes regarding memory handling. > For your convenience I have attached patches. > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Hallo, >> >> we have a Java application that is executing a larger sequence of SQL >> operations including table manipulations and content modifications within >> one connection. When we are running these operations through pgpool-II, the >> pgpool child process handling it always dies with a segmentation fault. But >> it's not always the same SQL Statement that is causing the segfault. >> >> Our setup is as follows: >> - pgpool-II-3.1 on a Linux-x86_64 server. We also encountered the >> segmentation fault with pgpool-II-3.0.4 before trying out version 3.1. >> - the pgpool configuration is reduced to a minimum, that is the connection >> cache, the master slave and the load balance mode are off. The replication >> mode is enabled but only one backend is defined. >> - PostgreSQL server version is 9.0.4 >> - the Java application uses the postgreSQL JDBC driver in version 9.0.801 >> >> Do you have an idea what might be causing this behavior? >> >> For some additional details I attached a backtrace. I can also provide the >> debug messages of the child process, if you want to have look at them. >> >> Thanks in advance. >> >> Ronny ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] How to configure only selected listen_addresses?
Hello, I think, for this purpose, you can use pool_hba.conf. You need to create this file and enable this property in pgpool.conf. Regards -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Gnanakumar Enviado el: viernes, 28 de octubre de 2011 05:24 Para: pgpool-general@pgfoundry.org Asunto: [?? Probable Spam] [Pgpool-general] How to configure only selected listen_addresses? Hi, Our production server is running PostgreSQL 8.2.3 and pgpool-II-2.0.1. How do I configure/set up *only selected* listen_addresses in pgpool.conf? For example, in my case, I would like to set it up in such a way that only 2 IP addresses are allowed: localhost and one other additional IP address (10.75.78.210). I don't want it to be just set to '*'. In pgpool doc here http://pgpool.projects.postgresql.org/pgpool-II/doc/tutorial-en.html, I don't find out anything explained on how to configure for selected IP addresses. In fact, I even tried out configuring multiple IP addresses separated by comma, but it is failing with the following exception: 2011-10-28 02:42:33 ERROR: pid 27119: could not resolve host name "127.0.0.1,10.75.78.210": Unknown host Regards, Gnanam ___ 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
Re: [Pgpool-general] pgpool-II child process is segfaulting
Hello Tatsuo, How I can download the latest stable release of pgpool-II 3.1, with the latest modifications developed? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii Enviado el: jueves, 27 de octubre de 2011 07:56 Para: ronny.wink...@communardo.de CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] pgpool-II child process is segfaulting Can you try CVS HEAD? After 3.1 released, I have committed some fixes regarding memory handling. For your convenience I have attached patches. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hallo, > > we have a Java application that is executing a larger sequence of SQL > operations including table manipulations and content modifications within one > connection. When we are running these operations through pgpool-II, the > pgpool child process handling it always dies with a segmentation fault. But > it's not always the same SQL Statement that is causing the segfault. > > Our setup is as follows: > - pgpool-II-3.1 on a Linux-x86_64 server. We also encountered the > segmentation fault with pgpool-II-3.0.4 before trying out version 3.1. > - the pgpool configuration is reduced to a minimum, that is the connection > cache, the master slave and the load balance mode are off. The replication > mode is enabled but only one backend is defined. > - PostgreSQL server version is 9.0.4 > - the Java application uses the postgreSQL JDBC driver in version 9.0.801 > > Do you have an idea what might be causing this behavior? > > For some additional details I attached a backtrace. I can also provide the > debug messages of the child process, if you want to have look at them. > > Thanks in advance. > > Ronny ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem with pgpool-II_3.1.0
Sorry, and thank you for the attention of the last email, I have resolved the
problem by changing this property in pgpool.conf
recovery_1st_stage_command = '/opt/pgsql/data/basebackup'
Now
recovery_1st_stage_command = 'basebackup'
Thank you for your time.
Regards.
De: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Lazaro Rubén García
Martinez
Enviado el: martes, 25 de octubre de 2011 02:36
Para: pgpool-general@pgfoundry.org
Asunto: [Pgpool-general] Problem with pgpool-II_3.1.0
Hello everyone in the list, I write you because I'm having a problem for doing
online_recovery with pgpool-II V 3.1.0, and I hope that you can help me. I am
configuring pgpool and postgreSQL in streaming replication mode, but when I try
to recover the standby node a backenError is returned and in the postgresql.log
file this error is shown:
LOG: connection authorized: user=postgres database=template1
LOG: statement: SELECT pgpool_recovery('/opt/pgsql/data/basebackup',
'10.13.4.205', '/opt/pgsql/data')
sh: /opt/pgsql/data//opt/pgsql/data/basebackup: No such file or directory
ERROR: pgpool_recovery failed
STATEMENT: SELECT pgpool_recovery('/opt/pgsql/data/basebackup', '10.13.4.205',
'/opt/pgsql/data')
The basebackup file is under /opt/pgsql/data/ but I do not know why the reason
for this error, the owner of basebackup file is the user postgres and the
permission over this file is755.
This is my pgpool.conf
I hope that you can help me, thank you very much for your time.
Regards.
#--
# CONNECTIONS
#--
# - pgpool Connection Settings -
listen_addresses = '*'
port =
socket_dir = '/tmp'
pcp_port = 9898
pcp_socket_dir = '/tmp'
# - Backend Connection Settings -
backend_hostname0 = '10.13.4.202'
# Host name or IP address to connect to for
backend 0
backend_port0 = 5432
# Port number for backend 0
backend_weight0 = 1
# Weight for backend 0 (only in load
balancing mode)
backend_data_directory0 = '/opt/pgsql/data'
# Data directory for backend 0
backend_flag0 = 'ALLOW_TO_FAILOVER'
# Controls various backend behavior
# ALLOW_TO_FAILOVER or DISALLOW_TO_FAILOVER
backend_hostname1 = '10.13.4.205'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/opt/pgsql/data'
backend_flag1 = 'ALLOW_TO_FAILOVER'
# - Authentication -
enable_pool_hba = off
authentication_timeout = 60
# - SSL Connections -
ssl = off
#ssl_key = './server.key'
#ssl_cert = './server.cert'
#ssl_ca_cert = ''
#ssl_ca_cert_dir = ''
#--
# POOLS
#--
# - Pool size -
num_init_children = 32
max_pool = 4
# - Life time -
child_life_time = 300
child_max_connections = 0
connection_life_time = 0
client_idle_limit = 0
#--
# LOGS
#--
# - Where to log -
log_destination = 'stderr'
# - What to log -
print_timestamp = on
log_connections = on
log_hostname = on
log_statement = on
log_per_node_statement = off
log_standby_delay = 'if_over_threshold'
# - Syslog specific -
syslog_facility = 'LOCAL0'
syslog_ident = 'pgpool'
# - Debug -
debug_level = 0
#--
# FILE LOCATIONS
#--
pid_file_name = '/var/run/pgpool/pgpool.pid'
logdir = '/opt/pgpool/pgpool_log'
#--
# CONNECTION POOLING
#--
connection_cache = on
reset_query_list = 'ABORT; DISCARD ALL'
#--
# REPLICATION MODE
#--
replication_mode = off
replicate_select = off
insert_lock = off
lobj_lock_table = ''
replication_stop_on_mismatch = off
failover_if_affected_tuples_mismatch = off
#--
# LOAD BALANCING MODE
#-
[Pgpool-general] Problem with pgpool-II_3.1.0
Hello everyone in the list, I write you because I'm having a problem for doing
online_recovery with pgpool-II V 3.1.0, and I hope that you can help me. I am
configuring pgpool and postgreSQL in streaming replication mode, but when I try
to recover the standby node a backenError is returned and in the postgresql.log
file this error is shown:
LOG: connection authorized: user=postgres database=template1
LOG: statement: SELECT pgpool_recovery('/opt/pgsql/data/basebackup',
'10.13.4.205', '/opt/pgsql/data')
sh: /opt/pgsql/data//opt/pgsql/data/basebackup: No such file or directory
ERROR: pgpool_recovery failed
STATEMENT: SELECT pgpool_recovery('/opt/pgsql/data/basebackup', '10.13.4.205',
'/opt/pgsql/data')
The basebackup file is under /opt/pgsql/data/ but I do not know why the reason
for this error, the owner of basebackup file is the user postgres and the
permission over this file is755.
This is my pgpool.conf
I hope that you can help me, thank you very much for your time.
Regards.
#--
# CONNECTIONS
#--
# - pgpool Connection Settings -
listen_addresses = '*'
port =
socket_dir = '/tmp'
pcp_port = 9898
pcp_socket_dir = '/tmp'
# - Backend Connection Settings -
backend_hostname0 = '10.13.4.202'
# Host name or IP address to connect to for
backend 0
backend_port0 = 5432
# Port number for backend 0
backend_weight0 = 1
# Weight for backend 0 (only in load
balancing mode)
backend_data_directory0 = '/opt/pgsql/data'
# Data directory for backend 0
backend_flag0 = 'ALLOW_TO_FAILOVER'
# Controls various backend behavior
# ALLOW_TO_FAILOVER or DISALLOW_TO_FAILOVER
backend_hostname1 = '10.13.4.205'
backend_port1 = 5432
backend_weight1 = 1
backend_data_directory1 = '/opt/pgsql/data'
backend_flag1 = 'ALLOW_TO_FAILOVER'
# - Authentication -
enable_pool_hba = off
authentication_timeout = 60
# - SSL Connections -
ssl = off
#ssl_key = './server.key'
#ssl_cert = './server.cert'
#ssl_ca_cert = ''
#ssl_ca_cert_dir = ''
#--
# POOLS
#--
# - Pool size -
num_init_children = 32
max_pool = 4
# - Life time -
child_life_time = 300
child_max_connections = 0
connection_life_time = 0
client_idle_limit = 0
#--
# LOGS
#--
# - Where to log -
log_destination = 'stderr'
# - What to log -
print_timestamp = on
log_connections = on
log_hostname = on
log_statement = on
log_per_node_statement = off
log_standby_delay = 'if_over_threshold'
# - Syslog specific -
syslog_facility = 'LOCAL0'
syslog_ident = 'pgpool'
# - Debug -
debug_level = 0
#--
# FILE LOCATIONS
#--
pid_file_name = '/var/run/pgpool/pgpool.pid'
logdir = '/opt/pgpool/pgpool_log'
#--
# CONNECTION POOLING
#--
connection_cache = on
reset_query_list = 'ABORT; DISCARD ALL'
#--
# REPLICATION MODE
#--
replication_mode = off
replicate_select = off
insert_lock = off
lobj_lock_table = ''
replication_stop_on_mismatch = off
failover_if_affected_tuples_mismatch = off
#--
# LOAD BALANCING MODE
#--
load_balance_mode = on
ignore_leading_white_space = on
white_function_list = ''
black_function_list = 'currval,lastval,nextval,setval'
#--
# MASTER/SLAVE MODE
#--
master_slave_mode = on
master_slave_sub_mode = 'stream'
sr_check_period = 360
sr_check_user = 'postgres'
delay_threshold = 1000
# - Special commands -
follow_master_command = ''
#--
# HEALTH CHECK
#--
health_check_period = 360
health_check_timeout = 20
health_check_user = 'postgres'
health_check_password = 'postgres'
#---
Re: [Pgpool-general] Problem when installing Pgpool-II
Tatsuo, as you can say I am modified the Makefile of pgpool-regclass, I'm change the path of pg_config and after execute make, this error is shown: make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found make: pg_config: Command not found gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -fwrapv -fpic -I. -I. -I/server -I/internal -D_GNU_SOURCE -c -o pgpool-regclass.o pgpool-regclass.c pgpool-regclass.c:26:22: error: postgres.h: No such file or directory pgpool-regclass.c:27:28: error: utils/builtins.h: No such file or directory pgpool-regclass.c:28:28: error: utils/syscache.h: No such file or directory pgpool-regclass.c:29:24: error: utils/elog.h: No such file or directory pgpool-regclass.c:30:31: error: catalog/namespace.h: No such file or directory pgpool-regclass.c:31:29: error: nodes/makefuncs.h: No such file or directory pgpool-regclass.c:32:33: error: commands/dbcommands.h: No such file or directory pgpool-regclass.c:33:18: error: fmgr.h: No such file or directory pgpool-regclass.c:34:21: error: funcapi.h: No such file or directory pgpool-regclass.c:42: warning: data definition has no type or storage class pgpool-regclass.c:42: warning: type defaults to ‘int’ in declaration of ‘PG_FUNCTION_INFO_V1’ pgpool-regclass.c:42: warning: parameter names (without types) in function declaration pgpool-regclass.c:44: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pgpool_regclass’ pgpool-regclass.c:46: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token pgpool-regclass.c:49: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token pgpool-regclass.c:52: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘MyDatabaseId’ pgpool-regclass.c:56: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘get_namespace_oid’ pgpool-regclass.c:60: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘pgpool_regclass’ pgpool-regclass.c:108: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token pgpool-regclass.c:143: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token pgpool-regclass.c:189: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘get_namespace_oid’ make: *** [pgpool-regclass.o] Error 1 Is there a parameter or configuration file to say to pgpool-regclass and pgpool-recovery where Postgresql are installed?? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 19 de octubre de 2011 11:01 Para: dev...@gunduz.org CC: Lazaro Rubén García Martinez; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II > On Wed, 2011-10-19 at 23:15 +0900, Tatsuo Ishii wrote: >> You should put /opt/pgsql/bin in your command search path. > > Why does --with-pgsql not picking up pg_config? It sounded a bit weird > to me to add pg_config under $PATH. It's configure's job to pick it up. Why? Even if configure picks up pg_config which is not in the command search path, subsequent make of pgpool-regclass will fail because of this anyway: PGXS = $(shell pg_config --pgxs) This is same as contrib Makefile of PostgreSQL(from PostgreSQL 9.0.5's pgbench Makefile). PG_CONFIG = pg_config PGXS := $(shell $(PG_CONFIG) --pgxs) -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Regards, > -- > Devrim GÜNDÜZ > Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com > PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer > Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr > http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem when installing Pgpool-II
Where I need to put this path? Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 19 de octubre de 2011 10:15 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II You should put /opt/pgsql/bin in your command search path. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Yes, if I execute pg_cofig > -bash: pg_cofig: command not found > > For executing pg_config I need to write the complete path for this command: > > /opt/pgsql/bin/pg_config. > > Regards. > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: miércoles, 19 de octubre de 2011 10:08 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II > > What I meant was, if you type "pg_config", it executes or do you get > "command not found"? > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Yes pg_config is installed, and it is under /opt/pgsql/bin directory. >> >> Pgpool is installed without problems, the problem is when a I try to install >> pgpool-regclass and pgpool-recovery functions. >> >> Regards. >> >> >> -Mensaje original- >> De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] >> Enviado el: miércoles, 19 de octubre de 2011 09:53 >> Para: Lazaro Rubén García Martinez >> CC: pgpool-general@pgfoundry.org >> Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II >> >> So you are sure that pg_config is installed. Is pg_config in your >> command search path? >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> English: http://www.sraoss.co.jp/index_en.php >> Japanese: http://www.sraoss.co.jp >> >>> Thank very much for your answer, I saw the FAQ, before sending the email. >>> In other moments I have installed pgpool and I do not have problems because >>> PostgreSQL has been installed with this parameters: >>> >>> ./configure --prefix=/opt/pgsql/ --enable-nls --bindir=/usr/bin/ >>> --datadir=/usr/share/pgsql --sysconfdir=/usr/etc/ --libdir=/usr/lib/ >>> --mandir=/usr/share/man/ --includedir=/usr/include/ --with-openssl >>> --with-ossp-uuid >>> make >>> make install >>> >>> But in this case, PostgreSQL was installed with this parameters: >>> >>> ./configure --prefix=/opt/pgsql/ --enable-nls >>> with-openssl --with-ossp-uuid >>> make >>> make install >>> >>> That means Postgresql libraries, binaries, header files and others are >>> under /opt/pgsql directory. >>> >>> I think this problem is because Pgpool can not found the components of >>> PostgreSQL that it use. >>> >>> Can you or someone in the list, help me to solve this problem, or I need to >>> install PostgreSQL in the other form?. >>> >>> I use, >>> Pgpool-II 3.1.0 >>> PostgreSQL 9.0.5 >>> CentOS 6.0 >>> >>> Thank you very much for your time. >>> >>> Regards. >>> >>> -Mensaje original- >>> De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] >>> Enviado el: martes, 18 de octubre de 2011 11:59 >>> Para: Lazaro Rubén García Martinez >>> CC: pgpool-general@pgfoundry.org >>> Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II >>> >>>> Hello everyone in the list, I try to install Pgpool-II version 3.1. The >>>> PostgreSQL server is installed under /opt/pgsql directory. >>>> >>>> I install pgpool with this parameters: >>>> ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ >>>> >>>> and all is good, the problem is when I try to install pgpool-regclass or >>>> pgpool-recovey functions, because this error is shown: >>>> >>>> make: pg_config: Command not found >>>> make: *** No targets. Stop. >>>> >>>> I was searching in google but I can not obtain a solution for this >>>> problem. >>>> >>>> Can anybody help me to solve this problem?? >>>> >>>> >>>> Thank you very much for your time. >>>> Regards. >>> >>> Did you take a look at FAQ #1? >>> >>> http://pgpool.projects.postgresql.org/FAQ.html >>> -- >>> Tatsuo Ishii >>> SRA OSS, Inc. Japan >>> English: http://www.sraoss.co.jp/index_en.php >>> Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem when installing Pgpool-II
Yes, if I execute pg_cofig -bash: pg_cofig: command not found For executing pg_config I need to write the complete path for this command: /opt/pgsql/bin/pg_config. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 19 de octubre de 2011 10:08 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II What I meant was, if you type "pg_config", it executes or do you get "command not found"? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Yes pg_config is installed, and it is under /opt/pgsql/bin directory. > > Pgpool is installed without problems, the problem is when a I try to install > pgpool-regclass and pgpool-recovery functions. > > Regards. > > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: miércoles, 19 de octubre de 2011 09:53 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II > > So you are sure that pg_config is installed. Is pg_config in your > command search path? > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Thank very much for your answer, I saw the FAQ, before sending the email. In >> other moments I have installed pgpool and I do not have problems because >> PostgreSQL has been installed with this parameters: >> >> ./configure --prefix=/opt/pgsql/ --enable-nls --bindir=/usr/bin/ >> --datadir=/usr/share/pgsql --sysconfdir=/usr/etc/ --libdir=/usr/lib/ >> --mandir=/usr/share/man/ --includedir=/usr/include/ --with-openssl >> --with-ossp-uuid >> make >> make install >> >> But in this case, PostgreSQL was installed with this parameters: >> >> ./configure --prefix=/opt/pgsql/ --enable-nls >> with-openssl --with-ossp-uuid >> make >> make install >> >> That means Postgresql libraries, binaries, header files and others are under >> /opt/pgsql directory. >> >> I think this problem is because Pgpool can not found the components of >> PostgreSQL that it use. >> >> Can you or someone in the list, help me to solve this problem, or I need to >> install PostgreSQL in the other form?. >> >> I use, >> Pgpool-II 3.1.0 >> PostgreSQL 9.0.5 >> CentOS 6.0 >> >> Thank you very much for your time. >> >> Regards. >> >> -Mensaje original- >> De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] >> Enviado el: martes, 18 de octubre de 2011 11:59 >> Para: Lazaro Rubén García Martinez >> CC: pgpool-general@pgfoundry.org >> Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II >> >>> Hello everyone in the list, I try to install Pgpool-II version 3.1. The >>> PostgreSQL server is installed under /opt/pgsql directory. >>> >>> I install pgpool with this parameters: >>> ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ >>> >>> and all is good, the problem is when I try to install pgpool-regclass or >>> pgpool-recovey functions, because this error is shown: >>> >>> make: pg_config: Command not found >>> make: *** No targets. Stop. >>> >>> I was searching in google but I can not obtain a solution for this problem. >>> >>> Can anybody help me to solve this problem?? >>> >>> >>> Thank you very much for your time. >>> Regards. >> >> Did you take a look at FAQ #1? >> >> http://pgpool.projects.postgresql.org/FAQ.html >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> English: http://www.sraoss.co.jp/index_en.php >> Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem when installing Pgpool-II
Yes pg_config is installed, and it is under /opt/pgsql/bin directory. Pgpool is installed without problems, the problem is when a I try to install pgpool-regclass and pgpool-recovery functions. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: miércoles, 19 de octubre de 2011 09:53 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II So you are sure that pg_config is installed. Is pg_config in your command search path? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Thank very much for your answer, I saw the FAQ, before sending the email. In > other moments I have installed pgpool and I do not have problems because > PostgreSQL has been installed with this parameters: > > ./configure --prefix=/opt/pgsql/ --enable-nls --bindir=/usr/bin/ > --datadir=/usr/share/pgsql --sysconfdir=/usr/etc/ --libdir=/usr/lib/ > --mandir=/usr/share/man/ --includedir=/usr/include/ --with-openssl > --with-ossp-uuid > make > make install > > But in this case, PostgreSQL was installed with this parameters: > > ./configure --prefix=/opt/pgsql/ --enable-nls > with-openssl --with-ossp-uuid > make > make install > > That means Postgresql libraries, binaries, header files and others are under > /opt/pgsql directory. > > I think this problem is because Pgpool can not found the components of > PostgreSQL that it use. > > Can you or someone in the list, help me to solve this problem, or I need to > install PostgreSQL in the other form?. > > I use, > Pgpool-II 3.1.0 > PostgreSQL 9.0.5 > CentOS 6.0 > > Thank you very much for your time. > > Regards. > > -Mensaje original- > De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] > Enviado el: martes, 18 de octubre de 2011 11:59 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II > >> Hello everyone in the list, I try to install Pgpool-II version 3.1. The >> PostgreSQL server is installed under /opt/pgsql directory. >> >> I install pgpool with this parameters: >> ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ >> >> and all is good, the problem is when I try to install pgpool-regclass or >> pgpool-recovey functions, because this error is shown: >> >> make: pg_config: Command not found >> make: *** No targets. Stop. >> >> I was searching in google but I can not obtain a solution for this problem. >> >> Can anybody help me to solve this problem?? >> >> >> Thank you very much for your time. >> Regards. > > Did you take a look at FAQ #1? > > http://pgpool.projects.postgresql.org/FAQ.html > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Problem when installing Pgpool-II
Thank very much for your answer, I saw the FAQ, before sending the email. In other moments I have installed pgpool and I do not have problems because PostgreSQL has been installed with this parameters: ./configure --prefix=/opt/pgsql/ --enable-nls --bindir=/usr/bin/ --datadir=/usr/share/pgsql --sysconfdir=/usr/etc/ --libdir=/usr/lib/ --mandir=/usr/share/man/ --includedir=/usr/include/ --with-openssl --with-ossp-uuid make make install But in this case, PostgreSQL was installed with this parameters: ./configure --prefix=/opt/pgsql/ --enable-nls with-openssl --with-ossp-uuid make make install That means Postgresql libraries, binaries, header files and others are under /opt/pgsql directory. I think this problem is because Pgpool can not found the components of PostgreSQL that it use. Can you or someone in the list, help me to solve this problem, or I need to install PostgreSQL in the other form?. I use, Pgpool-II 3.1.0 PostgreSQL 9.0.5 CentOS 6.0 Thank you very much for your time. Regards. -Mensaje original- De: Tatsuo Ishii [mailto:is...@sraoss.co.jp] Enviado el: martes, 18 de octubre de 2011 11:59 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problem when installing Pgpool-II > Hello everyone in the list, I try to install Pgpool-II version 3.1. The > PostgreSQL server is installed under /opt/pgsql directory. > > I install pgpool with this parameters: > ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ > > and all is good, the problem is when I try to install pgpool-regclass or > pgpool-recovey functions, because this error is shown: > > make: pg_config: Command not found > make: *** No targets. Stop. > > I was searching in google but I can not obtain a solution for this problem. > > Can anybody help me to solve this problem?? > > > Thank you very much for your time. > Regards. Did you take a look at FAQ #1? http://pgpool.projects.postgresql.org/FAQ.html -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Problem when installing Pgpool-II
Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory. I install pgpool with this parameters: ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ and all is good, the problem is when I try to install pgpool-regclass or pgpool-recovey functions, because this error is shown: make: pg_config: Command not found make: *** No targets. Stop. I was searching in google but I can not obtain a solution for this problem. Can anybody help me to solve this problem?? Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Problem when installing Pgpool-II
Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory. I install pgpool with this parameters: ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ The problem is when I try to install pgpool-regclass or pgpool-recovey functions, because this error is shown: make: pg_config: Command not found make: *** No targets. Stop. Can anybody help me to solve this problem?? Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Problem when installing Pgpool-II
Hello everyone in the list, I try to install Pgpool-II version 3.1. The PostgreSQL server is installed under /opt/pgsql directory. I install pgpool with this parameters: ./configure --prefix=/opt/pgpool --with-pgsql=/opt/pgsql/ The problem is when I try to install pgpool-regclass, because this error is shown: make: pg_config: Command not found make: *** No targets. Stop. Can anybody help me to solve this problem?? Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpoolAdmin 3.1.0 released
The link sending download pgpoolAdmin Version 3.0.3. The url for download pgpoolAdmin Version 3.1.0 from pgfoundry is: http://pgfoundry.org/frs/download.php/3149/pgpoolAdmin-3.1.0.tar.gz And the url sending is: http://pgfoundry.org/frs/download.php/2964/pgpoolAdmin-3.1.0.tar.gz As you can see these urls are different. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Nozomi Anzai Enviado el: viernes, 14 de octubre de 2011 12:10 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] pgpoolAdmin 3.1.0 released Pgpool Global Development Group is pleased to announce the availability of pgpoolAdmin 3.1.0, the latest stable version of an open source management tool for pgpool-II 3.1 series. --- Changes from pgpoolAdmin 3.1.0: --- * Replace functions deprecated in PHP 5.3 (Anzai) * Sync pgpool.conf Setting with pgpool-II 3.1 (Anzai) * Add new parameters and remove deleted parameters in pgpool-II 3.1 (Anzai) - new: follow_master_command, relcache_expire, backend_flag, sr_check_period, sr_check_user, sr_check_password, log_destination, syslog_facility, syslog_ident - deleted: pcp_timeout, backend_socket_dir * Add promote button in Master/Slave mode with streaming replication (Anzai) - This button is to execute pcp_promote_node. * Other small changes for pgpool-II 3.1 (Anzai) - When log_destination is syslog, Log button will be invisible. - Allow regex value in black_function_list and white_function_list. * Some fix (Anzai) - Change to save boolean values in pgpool.conf with on/off format. --- You can download pgpoolAdmin 3.1.0 from: http://pgfoundry.org/frs/download.php/2964/pgpoolAdmin-3.1.0.tar.gz If you find any problem, please post to: pgpool-general@pgfoundry.org -- Nozomi Anzai SRA OSS, Inc. Japan ___ 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
Re: [Pgpool-general] difference between master and primary node in streaming mode
Streaming replication mode is a master-slave replication system, this method allows to have a copy of the database, in a different database server. The purpose of this, is continues with the database service with slaves, in case of failures in the master or primary server. Streaming replication can be combined with host standby, allowing read queries in the slave or standby servers, for balancing the load between the servers. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Jeff Frost Enviado el: miércoles, 05 de octubre de 2011 02:39 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] difference between master and primary node in streaming mode What's the difference between the master and primary node in streaming replication mode? Occasionally, in my testing, I see this: Oct 5 11:36:08 31214-1-807393 pgpool[28871]: find_primary_node_repeatedly: waiting for finding a primary node Oct 5 11:36:08 31214-1-807393 pgpool[28871]: last message repeated 10 times Oct 5 11:36:08 31214-1-807393 pgpool[28871]: find_primary_node: 0 node is standby Oct 5 11:36:08 31214-1-807393 pgpool[28871]: last message repeated 10 times Oct 5 11:36:08 31214-1-807393 pgpool[28871]: find_primary_node: primary node id is 1 Oct 5 11:36:08 31214-1-807393 pgpool[28871]: failover: set new primary node: 1 Oct 5 11:36:08 31214-1-807393 pgpool[28871]: failover: set new master node: 0 Note that the primary and master are different. I understand that the primary node is considered whichever node is not in recovery mode, but what is the master? -- Jeff Frost CTO, PostgreSQL Experts, Inc. Phone: 1-888-PG-EXPRT x506 FAX: 415-762-5122 http://www.pgexperts.com/ ___ 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
Re: [Pgpool-general] Pgpool I vs Pgpool II
Thank you very much for the answer. Regards. -Mensaje original- De: Toshihiro Kitagawa [mailto:kitag...@sraoss.co.jp] Enviado el: lunes, 03 de octubre de 2011 03:23 Para: Lazaro Rubén García Martinez CC: Glyn Astill; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II Hi Lazaro, On Fri, 30 Sep 2011 08:40:59 -0430 Lazaro Rubén García Martinez wrote: > Thanks for the answer, One question, the patch proposed for some memory leaks > can be applied in Pgpool-II 3.1. The patch is not applicable to pgpool-II 3.1 without editing. I've attached the same patch for pgpool-II 3.1. It is unnecessary except for raw mode to apply these patches. Regards. -- Toshihiro Kitagawa SRA OSS, Inc. Japan > > Regards. > > -Mensaje original- > De: Toshihiro Kitagawa [mailto:kitag...@sraoss.co.jp] Enviado el: > viernes, 30 de septiembre de 2011 12:18 > Para: Lazaro Rubén García Martinez > CC: Glyn Astill; pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II > > Hi Lazaro, > > On Thu, 29 Sep 2011 08:44:41 -0430 > Lazaro Rubén García Martinez wrote: > > > Hi all, Is there an estimated date for release Pgpool-II version 3.0.5 and > > 3.1.1?. > > pgpool-II 3.0.5 is going to be released by the end of October. > The release time of pgpool-II 3.1.1 is undecided now. > > Regards. > > -- > Toshihiro Kitagawa > SRA OSS, Inc. Japan > > > > Regards. > > > > -Mensaje original- > > De: pgpool-general-boun...@pgfoundry.org > > [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Toshihiro > > Kitagawa Enviado el: miércoles, 28 de septiembre de 2011 10:38 > > Para: Glyn Astill > > CC: pgpool-general@pgfoundry.org > > Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II > > > > Hi Glyn, > > > > Thank you for your help. > > This problem will be fixed in next minor version up(3.0.5/3.1.1). > > > > -- > > Toshihiro Kitagawa > > SRA OSS, Inc. Japan > > > > On Wed, 28 Sep 2011 15:20:51 +0100 (BST) Glyn Astill > > wrote: > > > > > Hi Toshihiro, > > > > > > I can confirm that patch works and we no longer see the memory leak. > > > > > > Thanks > > > Glyn > > > > > > > > > > > > - Original Message - > > > > From: Toshihiro Kitagawa > > > > To: Glyn Astill ; takizo > > > > > > > > Cc: "pgpool-general@pgfoundry.org" > > > > > > > > Sent: Thursday, 22 September 2011, 10:57 > > > > Subject: Re: [Pgpool-general] Pgpool I vs Pgpool II > > > > > > > > Hi Glyn, takizo, > > > > > > > > I created a patch to fix a massive memory leak of raw mode. > > > > The patch which was posted before by Yoshiyuki seems correct. > > > > However, I think it's better to call > > > > pool_query_context_destroy() than free_parser(). > > > > > > > > Would you try an attached patch? > > > > > > > > The patch is for V3.0_STABLE branch, but it's applicable to > > > > pgpool-II 3.0.x too. > > > > > > > > Regards, > > > > > > > > -- > > > > Toshihiro Kitagawa > > > > SRA OSS, Inc. Japan > > > > > > > > On Thu, 8 Sep 2011 20:14:41 +0900 Toshihiro Kitagawa > > > > wrote: > > > > > > > >> Hi Glyn, takizo, > > > >> > > > >> Sorry for delay. > > > >> > > > >> I fixed some memory leaks in pgpool-II 3.1 and V3_0_STABLE. > > > >> But I guess memory leaks are remaining as you say. > > > >> > > > >> Surely, free_parser() which was commented out might be problem. > > > >> However, I think simply uncommenting leads unexpected new problem. > > > >> So we have to fix those carefully. > > > >> > > > >> I will investigate and fix memory problems which was posted to > > > >> this ML from now on. > > > >> > > > >> Regards, > > > >> > > > >> -- > > > >> Toshihiro Kitagawa > > > >> SRA OSS, Inc. Japan > > > >> > > > >> On Thu, 8 Sep 2011 16:22:50 +0800 takizo > > > >> wrote: > > > >> > > > >> > Glyn, > > > >> > > > > >> > Surely, I will try 2.3.3 :) > Thanks
Re: [Pgpool-general] Pgpool I vs Pgpool II
Thanks for the answer, One question, the patch proposed for some memory leaks can be applied in Pgpool-II 3.1. Regards. -Mensaje original- De: Toshihiro Kitagawa [mailto:kitag...@sraoss.co.jp] Enviado el: viernes, 30 de septiembre de 2011 12:18 Para: Lazaro Rubén García Martinez CC: Glyn Astill; pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II Hi Lazaro, On Thu, 29 Sep 2011 08:44:41 -0430 Lazaro Rubén García Martinez wrote: > Hi all, Is there an estimated date for release Pgpool-II version 3.0.5 and > 3.1.1?. pgpool-II 3.0.5 is going to be released by the end of October. The release time of pgpool-II 3.1.1 is undecided now. Regards. -- Toshihiro Kitagawa SRA OSS, Inc. Japan > > Regards. > > -Mensaje original- > De: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Toshihiro Kitagawa > Enviado el: miércoles, 28 de septiembre de 2011 10:38 > Para: Glyn Astill > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II > > Hi Glyn, > > Thank you for your help. > This problem will be fixed in next minor version up(3.0.5/3.1.1). > > -- > Toshihiro Kitagawa > SRA OSS, Inc. Japan > > On Wed, 28 Sep 2011 15:20:51 +0100 (BST) > Glyn Astill wrote: > > > Hi Toshihiro, > > > > I can confirm that patch works and we no longer see the memory leak. > > > > Thanks > > Glyn > > > > > > > > - Original Message - > > > From: Toshihiro Kitagawa > > > To: Glyn Astill ; takizo > > > Cc: "pgpool-general@pgfoundry.org" > > > Sent: Thursday, 22 September 2011, 10:57 > > > Subject: Re: [Pgpool-general] Pgpool I vs Pgpool II > > > > > > Hi Glyn, takizo, > > > > > > I created a patch to fix a massive memory leak of raw mode. > > > The patch which was posted before by Yoshiyuki seems correct. > > > However, I think it's better to call pool_query_context_destroy() > > > than free_parser(). > > > > > > Would you try an attached patch? > > > > > > The patch is for V3.0_STABLE branch, but it's applicable to > > > pgpool-II 3.0.x too. > > > > > > Regards, > > > > > > -- > > > Toshihiro Kitagawa > > > SRA OSS, Inc. Japan > > > > > > On Thu, 8 Sep 2011 20:14:41 +0900 > > > Toshihiro Kitagawa wrote: > > > > > >> Hi Glyn, takizo, > > >> > > >> Sorry for delay. > > >> > > >> I fixed some memory leaks in pgpool-II 3.1 and V3_0_STABLE. > > >> But I guess memory leaks are remaining as you say. > > >> > > >> Surely, free_parser() which was commented out might be problem. > > >> However, I think simply uncommenting leads unexpected new problem. > > >> So we have to fix those carefully. > > >> > > >> I will investigate and fix memory problems which was posted to > > >> this ML from now on. > > >> > > >> Regards, > > >> > > >> -- > > >> Toshihiro Kitagawa > > >> SRA OSS, Inc. Japan > > >> > > >> On Thu, 8 Sep 2011 16:22:50 +0800 > > >> takizo wrote: > > >> > > >> > Glyn, > > >> > > > >> > Surely, I will try 2.3.3 :) > > >> > Thanks a lot > > >> > > > >> > -- > > >> > Paul Ooi > > >> > > > >> > > > >> > > > >> > On Sep 8, 2011, at 4:00 PM, Glyn Astill wrote: > > >> > > > >> > > Hi takizo, > > >> > > > > >> > > We are currently using Pgpool-II 2.3.3 and it has been really > > > stable for us. Unless you're after a specific feature in Pgpool-II 3.x > > > you > > > could perhaps try it? > > >> > > > > >> > > So far I've had no luck with the patch posted by Yoshiyuki, > > > even with that patch there is still a massive memory leak in 3.0.4. It > > > would > > > appear that pool_proto_modules.c has lots commented out calls to > > > free_parser(), > > > many more than the single case that Yoshiyuki uncommented with his patch, > > > so > > > either there is a bit of a mess there that needs sorting out by someone > > > who > > > knows the overall logic, or the issue is elsew
Re: [Pgpool-general] Problems with md5 mode
I'm used pgpool-II with md5 authentication, you need to create a pool_password file and enabling pool_hba property in your pgpool.conf file, for more information about it, you can read the official documents of pgpool-II V 3.0.3, it is under pgpool-II V-3.0.3 package, an appointment: for generate the password of the user for connecting to the database, you need to create this user as OS user, and this user need permissions to read and write over pool_password file. Regards. -Mensaje original- De: Maria Antonia Lajus Marrero [mailto:malajuss...@gmail.com] Enviado el: jueves, 29 de septiembre de 2011 01:23 Para: Lazaro Rubén García Martinez Asunto: Re: [Pgpool-general] Problems with md5 mode Hello Lazaro, Pgpool-II 3.0.3 with PostgreSQL 8.3.9 and Heatbeat 2.1.3. Do you have any advise for this? Thanks. 2011/9/29, Lazaro Rubén García Martinez : > What version of pgpool do you use? > > Regards > > -Mensaje original- > De: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Maria Antonia > Lajus Marrero > Enviado el: jueves, 29 de septiembre de 2011 11:56 > Para: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] Problems with md5 mode > > I need a PGPool configuration that guarantee security and safety, > because I've tried a configuration with "md5" and gives me error. I > can not restrict access to the databases in the cluster. Neither in > the PostgreSQL pg_hba.conf file or in the pgpool_hba.conf file of > pgPool-II. > > This is the error: > MD5 authentication is unsupported in replication, master-slave and > parallel modes > > Please answer me. > thank you very much > ___ > 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
Re: [Pgpool-general] Problems with md5 mode
What version of pgpool do you use? Regards -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Maria Antonia Lajus Marrero Enviado el: jueves, 29 de septiembre de 2011 11:56 Para: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Problems with md5 mode I need a PGPool configuration that guarantee security and safety, because I've tried a configuration with "md5" and gives me error. I can not restrict access to the databases in the cluster. Neither in the PostgreSQL pg_hba.conf file or in the pgpool_hba.conf file of pgPool-II. This is the error: MD5 authentication is unsupported in replication, master-slave and parallel modes Please answer me. thank you very much ___ 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
Re: [Pgpool-general] PgPool Question
For establish the high availability of Pgpool-II, you can use any HA software like heartbeat, I never used this tool, but I know that it allows start other instance of Pgpool-II if the first shuts down. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii Enviado el: jueves, 29 de septiembre de 2011 09:01 Para: mickamus...@gmail.com CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] PgPool Question > Hi, I've 3 server. > > Server A with Pgpool in streaming replication mode. > Server B with Postgres Primary database . > Server C with Postgres Standby database. > > > I would like to know what will happen if Server A goes down ? If A goes down, pgpool goes down of course, but does not affect B and C. > I plan to > connect directly the database B instead of A until the server A restart. > > > What do you think ? That should work. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ 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
Re: [Pgpool-general] Pgpool I vs Pgpool II
Hi all, Is there an estimated date for release Pgpool-II version 3.0.5 and 3.1.1?. Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Toshihiro Kitagawa Enviado el: miércoles, 28 de septiembre de 2011 10:38 Para: Glyn Astill CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Pgpool I vs Pgpool II Hi Glyn, Thank you for your help. This problem will be fixed in next minor version up(3.0.5/3.1.1). -- Toshihiro Kitagawa SRA OSS, Inc. Japan On Wed, 28 Sep 2011 15:20:51 +0100 (BST) Glyn Astill wrote: > Hi Toshihiro, > > I can confirm that patch works and we no longer see the memory leak. > > Thanks > Glyn > > > > - Original Message - > > From: Toshihiro Kitagawa > > To: Glyn Astill ; takizo > > Cc: "pgpool-general@pgfoundry.org" > > Sent: Thursday, 22 September 2011, 10:57 > > Subject: Re: [Pgpool-general] Pgpool I vs Pgpool II > > > > Hi Glyn, takizo, > > > > I created a patch to fix a massive memory leak of raw mode. > > The patch which was posted before by Yoshiyuki seems correct. > > However, I think it's better to call pool_query_context_destroy() > > than free_parser(). > > > > Would you try an attached patch? > > > > The patch is for V3.0_STABLE branch, but it's applicable to > > pgpool-II 3.0.x too. > > > > Regards, > > > > -- > > Toshihiro Kitagawa > > SRA OSS, Inc. Japan > > > > On Thu, 8 Sep 2011 20:14:41 +0900 > > Toshihiro Kitagawa wrote: > > > >> Hi Glyn, takizo, > >> > >> Sorry for delay. > >> > >> I fixed some memory leaks in pgpool-II 3.1 and V3_0_STABLE. > >> But I guess memory leaks are remaining as you say. > >> > >> Surely, free_parser() which was commented out might be problem. > >> However, I think simply uncommenting leads unexpected new problem. > >> So we have to fix those carefully. > >> > >> I will investigate and fix memory problems which was posted to > >> this ML from now on. > >> > >> Regards, > >> > >> -- > >> Toshihiro Kitagawa > >> SRA OSS, Inc. Japan > >> > >> On Thu, 8 Sep 2011 16:22:50 +0800 > >> takizo wrote: > >> > >> > Glyn, > >> > > >> > Surely, I will try 2.3.3 :) > >> > Thanks a lot > >> > > >> > -- > >> > Paul Ooi > >> > > >> > > >> > > >> > On Sep 8, 2011, at 4:00 PM, Glyn Astill wrote: > >> > > >> > > Hi takizo, > >> > > > >> > > We are currently using Pgpool-II 2.3.3 and it has been really > > stable for us. Unless you're after a specific feature in Pgpool-II 3.x you > > could perhaps try it? > >> > > > >> > > So far I've had no luck with the patch posted by Yoshiyuki, > > even with that patch there is still a massive memory leak in 3.0.4. It > > would > > appear that pool_proto_modules.c has lots commented out calls to > > free_parser(), > > many more than the single case that Yoshiyuki uncommented with his patch, > > so > > either there is a bit of a mess there that needs sorting out by someone who > > knows the overall logic, or the issue is elsewhere. > >> > > > >> > > Glyn > >> > > > >> > > From: takizo > >> > > To: Glyn Astill > >> > > Cc: "pgpool-general@pgfoundry.org" > > > >> > > Sent: Thursday, 8 September 2011, 1:48 > >> > > Subject: Re: [Pgpool-general] Pgpool I vs Pgpool II > >> > > > >> > > Gyln, > >> > > > >> > > Thanks. I happened to read through the thread after posted the > > mail. It seems like I have to stick with Pgpool I until the developer is > > free. > >> > > > >> > > -- > >> > > takizo > >> > > > >> > > > >> > > > >> > > On Sep 7, 2011, at 10:53 PM, Glyn Astill wrote: > >> > > > >> > >> Hi takizo, > >> > >> > >> > >> Yes this bug has been seen by numerous people on the list, > > Yoshiyuki Asaba has posted a patch, however there has been no response from > > the > > main Pgpool II developers. > >> > >> > >> > >> I did ask a few times, and also asked if we'd be better > > testing 3.1, but alas still no response. I can only assume the devs are > > busy or > > otherwise indisposed. > >> > >> > >> > >> See the thread below for the patch. > >> > >> > >> > >> > > http://www.mail-archive.com/pgpool-general@pgfoundry.org/msg03141.html > >> > >> > >> > >> Glyn > >> > >> > >> > >> From: takizo > >> > >> To: pgpool-general@pgfoundry.org > >> > >> Sent: Wednesday, 7 September 2011, 15:02 > >> > >> Subject: [Pgpool-general] Pgpool I vs Pgpool II > >> > >> > >> > >> Hi all, > >> > >> > >> > >> Today I have upgraded Pgpool I to Pgpool II. And I had to > > roll back to Pgpool I due to memory hunger issue. > >> > >> > >> > >> My server is configured with > >> > >> PostgreSQL 8.2, > >> > >> running on FreeBSD 8.2 > >> > >> Intel Xeon box with 4 CPUs with Quad Core, total of 16 cores > >> > >> Memory with 24GB > >> > >> > >> > >> * While running on Pgpool I > >> > >> I do no have memory hunger issue. On postgresql.conf, I have > > max_connections=200 and shared_buffers=2GB.
Re: [Pgpool-general] problem with replication
pgpool_status file is saved under the directory logdir = ''. You can find this property in your pgpool.conf file, and you must assign the appropriate permissions over the path for pgpool_status. Regards. -Mensaje original- De: Cristina Bulfon [mailto:cristina.bul...@roma1.infn.it] Enviado el: lunes, 26 de septiembre de 2011 05:02 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] problem with replication Hello, thanks for the answer. I don't have the file pgpool_status and yes, backend1 can receive connection from pgpool node, just for testing the authentication method (at the moment) is "trust" ciao cristina On Sep 23, 2011, at 4:10 PM, Lazaro Rubén García Martinez wrote: > Pgpool, saves the status node in pgpool_status file, for example if > you stop one PostgreSQL node manually and pgpool performs a health > check and detects that this node is down, the result is saved in > pgpool_status for preventing future replication problems, but if you > start the backend manually, this continues down for pgpool, if you > are sure that the two servers are sync, you can stop pgpool, delete > pgpool_status and start up pgpool again, in other way you can stop > backend1 and perform and online recovery with pgpool. > > Other options, can backend1 receive connections from pgpool?? Is > there any rule in pg_hba.conf of backend1 for allows pgpool connect > to it? What is the authentication method used?? > > > Regards. > > -Mensaje original- > De: pgpool-general-boun...@pgfoundry.org > [mailto:pgpool-general-boun...@pgfoundry.org > ] En nombre de Cristina Bulfon > Enviado el: viernes, 23 de septiembre de 2011 08:58 > Para: pgpool-general@pgfoundry.org > Asunto: [Pgpool-general] problem with replication > > Hello, > > I have the following layout, > > - one computer is running pgpool-II-3.10 and postgresql 8.4.7-1 > (backend 0) > - one computer running postgresql 8.4.7-1 (backend 1) > > I have used the pgpool.conf.sample.replication for my set up and if I > try to create both the DB's user and the database (using port ) I > don't see the replication on both backends. > I also try to see the pcp comunication and the backend1 seems to be > down even if postgres is running on this node. > > Any help is appreciate. > > Thanks > > cristina > > ___ > 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
Re: [Pgpool-general] problem with replication
Pgpool, saves the status node in pgpool_status file, for example if you stop one PostgreSQL node manually and pgpool performs a health check and detects that this node is down, the result is saved in pgpool_status for preventing future replication problems, but if you start the backend manually, this continues down for pgpool, if you are sure that the two servers are sync, you can stop pgpool, delete pgpool_status and start up pgpool again, in other way you can stop backend1 and perform and online recovery with pgpool. Other options, can backend1 receive connections from pgpool?? Is there any rule in pg_hba.conf of backend1 for allows pgpool connect to it? What is the authentication method used?? Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Cristina Bulfon Enviado el: viernes, 23 de septiembre de 2011 08:58 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] problem with replication Hello, I have the following layout, - one computer is running pgpool-II-3.10 and postgresql 8.4.7-1 (backend 0) - one computer running postgresql 8.4.7-1 (backend 1) I have used the pgpool.conf.sample.replication for my set up and if I try to create both the DB's user and the database (using port ) I don't see the replication on both backends. I also try to see the pcp comunication and the backend1 seems to be down even if postgres is running on this node. Any help is appreciate. Thanks cristina ___ 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
Re: [Pgpool-general] Replicate selected table
I think this is not possible. Regards. De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Micka Enviado el: jueves, 22 de septiembre de 2011 11:00 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] Replicate selected table Hello, I've two server : A & B. In the Server A, I've the table 1 and 3 In the Server B, I've the table 2 and 4. I would like to know if the server A can replicate the table 1 and 3 to the server B. And the server B can replicate the table 2 and 4 to the server A ? Thank you, ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat
I recommend you see this link: http://linuxsilo.net/articles/postgresql-pgpool.html Regards. -Mensaje original- De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Maria Antonia Lajus Marrero Enviado el: martes, 20 de septiembre de 2011 01:49 Para: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Pgpool-II connection problems when monitoring Heartbeat 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 = '/var/run/pgpool/pgpool.pid' 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 = 'balanceador03' 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 = '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
Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode?
'replication_mode = true' means sincronous replication with pgpool-II, pgpool_walrecrunning function is used for streaming replication, configuring pgpool-II in master/slave sub-mode stream. Regards. De: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-boun...@pgfoundry.org] En nombre de Sandeep Thakkar Enviado el: lunes, 19 de septiembre de 2011 01:32 Para: Tatsuo Ishii CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode? Thanks Tatsuo. By streaming replication mode, you mean the 'replication_mode = true' in pgpool.conf? If I use pgpool-II-3.0.3, and configure it in Master/Slave mode with sub mode as 'stream', then I do not need this function., right? Sandeep. From: Tatsuo Ishii To: sandee...@yahoo.com Cc: pgpool-general@pgfoundry.org Sent: Saturday, September 17, 2011 1:40 PM Subject: Re: [Pgpool-general] Is pgpool_walrecrunning needed in Master/Slave mode? > I read the 3.0.3 docs and found that pgpool_walrecrunning() should be used > only in replication mode, and that too when somebody is using the > failure/online recovery feature of pgPoll-II. pgpool_walrecrunning is only usefull for streaming replication mode in 3.0.x. > At the same time, I found that this function has undergone some change: > " > > Now "pgpool_walrecrunning()" was not used. pgpool-II used to consider the > node that is promoted a primary node using the function. Now, pgpool-II waits > for completing of the promotion to primary node because it did not work as we > intended. But we still have a problem that pgpool-II waits while > recovery_timeout, when there is no primary node(Kitagawa) > " > > Can someone elaborate this please? Also, I assume that I need this function > only when I setup pgPool-II in replication mode. In pgpool-II 3.1 the function is not used anymore even in streaming replication mode. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] PGpool tuning to improve performance
As I know, Pgpool-II only balances the queries among backends, When a client connect to pgpool, Pgpool gives to client a sesion in that all select queries works, and it session is obtained by the parameters backend_weigh in pgpool.conf, with these parameters you can send more load to one server. If you need improve the performance of your queries, I recommend you to tuning your servers. Remember that pgpool is a program that intercepts every SQL query and sends it to one or all servers. Regards. De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Sachin [sysad...@indicussoftware.com] Enviado el: martes, 28 de junio de 2011 8:38 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] PGpool tuning to improve performance Hello, I have pgpool & posgtres 8.4 installed successfully. Load balancing is also working average. I want to improve or boost up performance for load balancing. Right now, we are testing SELECT queries to database. Will you please guide us if somehow I'll able to improve it's performance.? Regards, Sachin ___ 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
Re: [Pgpool-general] parameters replication_stop_on_mismatch
No necesary, but if the parameter is set to true, when a problem occurs, the node is degenerated and the client never knows that in the database server occurred an error, in this case a desynchronization between database servers of the cluster. Regards. De: Diego Ayala [netdieg...@gmail.com] Enviado el: lunes, 27 de junio de 2011 10:36 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] parameters replication_stop_on_mismatch Thanks Lazaro, then to have identical servers must be true and false given the option of non-identical? I'm beginning to PGPool-II is why I do not quite understand El 27 de junio de 2011 09:53, Lazaro Rubén García Martinez mailto:lgarc...@vnz.uci.cu>> escribió: I prefer set this parameter to true by knowing if there is a synchronization problem in the servers, in the other hand, if in the servers there is a problem like this, the users should not be affected. In the oficial documentation says: When set to true, if all backends don't return the same packet kind, the backends that differ from most frequent result set are degenerated. A typical use case is a SELECT statement part of a transaction, replicate_select set to true, and SELECT returning a different number of rows among backends. Non-SELECT statements might trigger this though. For example, a backend succeeded in an UPDATE, while others failed. Note that pgpool does NOT examine the content of records returned by SELECT. If set to false, the session is terminated and the backends are not degenerated. Default is false. Regards. De: pgpool-general-boun...@pgfoundry.org<mailto:pgpool-general-boun...@pgfoundry.org> [pgpool-general-boun...@pgfoundry.org<mailto:pgpool-general-boun...@pgfoundry.org>] En nombre de Diego Ayala [netdieg...@gmail.com<mailto:netdieg...@gmail.com>] Enviado el: lunes, 27 de junio de 2011 8:59 Para: pgpool-general@pgfoundry.org<mailto:pgpool-general@pgfoundry.org> Asunto: [Pgpool-general] parameters replication_stop_on_mismatch Good morning, I have installed the 3.0.3 version of pgPool-II, I wonder what benefits would have true or false triggering, the parameter replication_stop_on_mismatch, which is the recommended option ..? thanks, Diego ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] parameters replication_stop_on_mismatch
I prefer set this parameter to true by knowing if there is a synchronization problem in the servers, in the other hand, if in the servers there is a problem like this, the users should not be affected. In the oficial documentation says: When set to true, if all backends don't return the same packet kind, the backends that differ from most frequent result set are degenerated. A typical use case is a SELECT statement part of a transaction, replicate_select set to true, and SELECT returning a different number of rows among backends. Non-SELECT statements might trigger this though. For example, a backend succeeded in an UPDATE, while others failed. Note that pgpool does NOT examine the content of records returned by SELECT. If set to false, the session is terminated and the backends are not degenerated. Default is false. Regards. De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Diego Ayala [netdieg...@gmail.com] Enviado el: lunes, 27 de junio de 2011 8:59 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] parameters replication_stop_on_mismatch Good morning, I have installed the 3.0.3 version of pgPool-II, I wonder what benefits would have true or false triggering, the parameter replication_stop_on_mismatch, which is the recommended option ..? thanks, Diego ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] Error during md5 authentication
Toshihiro, thank you very much for your answer and patch, I proved it and works as expected. One other error that I see in pgpool log file is related with SSL conection, these are the SSL configurateion parameters in my pgpool.conf # If true, enable SSL support for both frontend and backend connections. # note that you must also set ssl_key and ssl_cert for SSL to work in # the frontend connections. ssl = true # path to the SSL private key file ssl_key = '/opt/pgpool/ssl/server.key' # path to the SSL public certificate file ssl_cert = '/opt/pgpool/ssl/server.cert' But in pgpool log file this error is shown: 2011-06-23 10:53:33LOG:pid 3996: connection received: host=psp01.psp.vnz.uci.cu port=51498 2011-06-23 10:53:33DEBUG: pid 3996: Protocol Major: 1234 Minor: 5679 database: user: 2011-06-23 10:53:33DEBUG: pid 3996: SSLRequest from client 2011-06-23 10:53:33ERROR: pid 3996: pool_ssl: Loading SSL certificate: No such file or directory 2011-06-23 10:53:33DEBUG: pid 3996: Protocol Major: 3 Minor: 0 database: tesis user: postgres 2011-06-23 10:53:33DEBUG: pid 3996: new_connection: connecting 0 backend 2011-06-23 10:53:33DEBUG: pid 3996: new_connection: connecting 1 backend 2011-06-23 10:53:33DEBUG: pid 3996: new_connection: skipping slot 1 because backend_status = 3 2011-06-23 10:53:33DEBUG: pid 3996: pool_ssl: sending client->server SSL request 2011-06-23 10:53:33DEBUG: pid 3996: pool_ssl: client->server SSL response: N 2011-06-23 10:53:33DEBUG: pid 3996: pool_ssl: server doesn't want to talk SSL 2011-06-23 10:53:33DEBUG: pid 3996: pool_read_message_length: slot: 0 length: 12 2011-06-23 10:53:33DEBUG: pid 3996: pool_do_auth: auth kind:5 2011-06-23 10:53:33DEBUG: pid 3996: trying md5 authentication 2011-06-23 10:53:33DEBUG: pid 3996: read_password_packet_password: failed to read password packet "p" 2011-06-23 10:53:33DEBUG: pid 3996: do_md5: read_password_packet failed 2011-06-23 10:53:33DEBUG: pid 3996: do_md5failed in slot 0 2011-06-23 10:53:35DEBUG: pid 3996: I am 3996 accept fd 14 2011-06-23 10:53:35LOG:pid 3996: connection received: host=psp01.psp.vnz.uci.cu port=51512 2011-06-23 10:53:35DEBUG: pid 3996: Protocol Major: 1234 Minor: 5679 database: user: 2011-06-23 10:53:35DEBUG: pid 3996: SSLRequest from client 2011-06-23 10:53:35ERROR: pid 3996: pool_ssl: Loading SSL certificate: system lib 2011-06-23 10:53:35DEBUG: pid 3996: Protocol Major: 3 Minor: 0 database: tesis user: postgres 2011-06-23 10:53:35DEBUG: pid 3996: new_connection: connecting 0 backend 2011-06-23 10:53:35DEBUG: pid 3996: new_connection: connecting 1 backend 2011-06-23 10:53:35DEBUG: pid 3996: new_connection: skipping slot 1 because backend_status = 3 2011-06-23 10:53:35DEBUG: pid 3996: pool_ssl: sending client->server SSL request 2011-06-23 10:53:35DEBUG: pid 3996: pool_ssl: client->server SSL response: N 2011-06-23 10:53:35DEBUG: pid 3996: pool_ssl: server doesn't want to talk SSL 2011-06-23 10:53:35DEBUG: pid 3996: pool_read_message_length: slot: 0 length: 12 Can you tell my the reason of this error? Regards. De: Toshihiro Kitagawa [kitag...@sraoss.co.jp] Enviado el: miércoles, 08 de junio de 2011 6:02 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Error during md5 authentication On Mon, 6 Jun 2011 19:28:24 +0900 Toshihiro Kitagawa wrote: > On Sun, 5 Jun 2011 22:57:21 -0430 > Lazaro Rubén García Martinez wrote: > > > Hello, every one in the list, When a try to connect to postgresql servers > > through pgpool-II using md5 authetication method, in pgpool-II log file, > > this error is shown: > > > > trying md5 authentication > > 2011-06-05 18:00:55DEBUG: pid 8147: > > read_password_packet_password: failed to read password packet "p" > > 2011-06-05 18:00:55ERROR: pid 8147: do_md5: > > read_password_packet failed > > 2011-06-05 18:00:55DEBUG: pid 8147: do_md5failed in > > slot 0 > > > > Can any body tell my, why is the reason of this problem??? > > I
[Pgpool-general] The connection close
Hello, every one in the list, when I conect to pgpool by psql, and stop one PostgreSQL server, the connection closes, failover is performed but the transaction executed by pgpool is aborted, but I don't know why the transaction is aborted if pgpool make failover??? I think that this onluy occurs using psql. Is this right?? Why is the cause of the error?? Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Error with pgbench and Pgpool-II
Hello every one in the list. At this moment I am writing you, because I am proving the load balance of pgpool-II with pgbench, but when I stop one PostgreSQL node, the test fails, but in this case, Pgpool-II Should not make a failover, degenerate the node, and continue with the test, or this situation only occurs with pgbench? I hope your answers, because this problem has me very worried. Thank you very much for your time. Regards. pgbench -U postgres -h 10.13.4.200 -p -n -f /home/pasaporte/Desktop/tesisPredefensa/balanceCarga/test.sql -c 80 -t 100 tesis Password: Client 23 aborted in state 2: FATAL: terminating connection due to administrator command Client 25 aborted in state 2: FATAL: terminating connection due to administrator command Client 41 aborted in state 1: FATAL: terminating connection due to administrator command Client 52 aborted in state 1: FATAL: terminating connection due to administrator command Client 58 aborted in state 0: FATAL: terminating connection due to administrator command Client 67 aborted in state 2: FATAL: terminating connection due to administrator command Client 70 aborted in state 2: FATAL: terminating connection due to administrator command Client 71 aborted in state 0: FATAL: terminating connection due to administrator command Client 77 aborted in state 2. Probably the backend died while processing. Client 0 aborted in state 2. Probably the backend died while processing. Client 1 aborted in state 0. Probably the backend died while processing. Client 2 aborted in state 0. Probably the backend died while processing. Client 3 aborted in state 0. Probably the backend died while processing. Client 4 aborted in state 3. Probably the backend died while processing. Client 5 aborted in state 2. Probably the backend died while processing. Client 7 aborted in state 1. Probably the backend died while processing. Client 8 aborted in state 3. Probably the backend died while processing. Client 9 aborted in state 0. Probably the backend died while processing. Client 10 aborted in state 1. Probably the backend died while processing. Client 11 aborted in state 0. Probably the backend died while processing. Client 12 aborted in state 0. Probably the backend died while processing. Client 13 aborted in state 0. Probably the backend died while processing. Client 14 aborted in state 0. Probably the backend died while processing. Client 16 aborted in state 1. Probably the backend died while processing. Client 17 aborted in state 3. Probably the backend died while processing. Client 18 aborted in state 2. Probably the backend died while processing. Client 19 aborted in state 0. Probably the backend died while processing. Client 20 aborted in state 3. Probably the backend died while processing. Client 21 aborted in state 2. Probably the backend died while processing. Client 22 aborted in state 0. Probably the backend died while processing. Client 24 aborted in state 0. Probably the backend died while processing. Client 26 aborted in state 1. Probably the backend died while processing. Client 27 aborted in state 1. Probably the backend died while processing. Client 28 aborted in state 1. Probably the backend died while processing. Client 30 aborted in state 2. Probably the backend died while processing. Client 31 aborted in state 2. Probably the backend died while processing. Client 33 aborted in state 1. Probably the backend died while processing. Client 34 aborted in state 2. Probably the backend died while processing. Client 35 aborted in state 0. Probably the backend died while processing. Client 36 aborted in state 2. Probably the backend died while processing. Client 37 aborted in state 3. Probably the backend died while processing. Client 38 aborted in state 1. Probably the backend died while processing. Client 39 aborted in state 1. Probably the backend died while processing. Client 40 aborted in state 2. Probably the backend died while processing. Client 42 aborted in state 0. Probably the backend died while processing. Client 43 aborted in state 0. Probably the backend died while processing. Client 44 aborted in state 1. Probably the backend died while processing. Client 45 aborted in state 3. Probably the backend died while processing. Client 46 aborted in state 3. Probably the backend died while processing. Client 47 aborted in state 1. Probably the backend died while processing. Client 48 aborted in state 0. Probably the backend died while processing. Client 50 aborted in state 1. Probably the backend died while processing. Client 51 aborted in state 2. Probably the backend died while processing. Client 53 aborted in state 2. Probably the backend died while processing. Client 54 aborted in state 0. Probably the backend died while processing. Client 56 aborted in state 1. Probably the backend died while processing. Client 57 aborted in state 1. Probably the backend died while processing. Client 59 aborted in state 3. Probably the backend died while proce
[Pgpool-general] Error ocurring with pgbench
Hello every one in the list. At this moment I am writing you, because I am proving the load balance of pgpool-II with pgbench, but when I stop one PostgreSQL node, the test fails, but in this case, Pgpool-II Should not make a failover, degenerate the node, and continue with the test, or this situation only occurs with pgbench? I hope your answers, because this problem has me very worried. Thank you very much for your time. Regards. pgbench -U postgres -h 10.13.4.200 -p -n -f /home/pasaporte/Desktop/tesisPredefensa/balanceCarga/test.sql -c 80 -t 100 tesis Password: Client 23 aborted in state 2: FATAL: terminating connection due to administrator command Client 25 aborted in state 2: FATAL: terminating connection due to administrator command Client 41 aborted in state 1: FATAL: terminating connection due to administrator command Client 52 aborted in state 1: FATAL: terminating connection due to administrator command Client 58 aborted in state 0: FATAL: terminating connection due to administrator command Client 67 aborted in state 2: FATAL: terminating connection due to administrator command Client 70 aborted in state 2: FATAL: terminating connection due to administrator command Client 71 aborted in state 0: FATAL: terminating connection due to administrator command Client 77 aborted in state 2. Probably the backend died while processing. Client 0 aborted in state 2. Probably the backend died while processing. Client 1 aborted in state 0. Probably the backend died while processing. Client 2 aborted in state 0. Probably the backend died while processing. Client 3 aborted in state 0. Probably the backend died while processing. Client 4 aborted in state 3. Probably the backend died while processing. Client 5 aborted in state 2. Probably the backend died while processing. Client 7 aborted in state 1. Probably the backend died while processing. Client 8 aborted in state 3. Probably the backend died while processing. Client 9 aborted in state 0. Probably the backend died while processing. Client 10 aborted in state 1. Probably the backend died while processing. Client 11 aborted in state 0. Probably the backend died while processing. Client 12 aborted in state 0. Probably the backend died while processing. Client 13 aborted in state 0. Probably the backend died while processing. Client 14 aborted in state 0. Probably the backend died while processing. Client 16 aborted in state 1. Probably the backend died while processing. Client 17 aborted in state 3. Probably the backend died while processing. Client 18 aborted in state 2. Probably the backend died while processing. Client 19 aborted in state 0. Probably the backend died while processing. Client 20 aborted in state 3. Probably the backend died while processing. Client 21 aborted in state 2. Probably the backend died while processing. Client 22 aborted in state 0. Probably the backend died while processing. Client 24 aborted in state 0. Probably the backend died while processing. Client 26 aborted in state 1. Probably the backend died while processing. Client 27 aborted in state 1. Probably the backend died while processing. Client 28 aborted in state 1. Probably the backend died while processing. Client 30 aborted in state 2. Probably the backend died while processing. Client 31 aborted in state 2. Probably the backend died while processing. Client 33 aborted in state 1. Probably the backend died while processing. Client 34 aborted in state 2. Probably the backend died while processing. Client 35 aborted in state 0. Probably the backend died while processing. Client 36 aborted in state 2. Probably the backend died while processing. Client 37 aborted in state 3. Probably the backend died while processing. Client 38 aborted in state 1. Probably the backend died while processing. Client 39 aborted in state 1. Probably the backend died while processing. Client 40 aborted in state 2. Probably the backend died while processing. Client 42 aborted in state 0. Probably the backend died while processing. Client 43 aborted in state 0. Probably the backend died while processing. Client 44 aborted in state 1. Probably the backend died while processing. Client 45 aborted in state 3. Probably the backend died while processing. Client 46 aborted in state 3. Probably the backend died while processing. Client 47 aborted in state 1. Probably the backend died while processing. Client 48 aborted in state 0. Probably the backend died while processing. Client 50 aborted in state 1. Probably the backend died while processing. Client 51 aborted in state 2. Probably the backend died while processing. Client 53 aborted in state 2. Probably the backend died while processing. Client 54 aborted in state 0. Probably the backend died while processing. Client 56 aborted in state 1. Probably the backend died while processing. Client 57 aborted in state 1. Probably the backend died while processing. Client 59 aborted in state 3. Probably the backend died while proc
[Pgpool-general] Error during md5 authentication
Hello, every one in the list, When a try to connect to postgresql servers through pgpool-II using md5 authetication method, in pgpool-II log file, this error is shown: trying md5 authentication 2011-06-05 18:00:55DEBUG: pid 8147: read_password_packet_password: failed to read password packet "p" 2011-06-05 18:00:55ERROR: pid 8147: do_md5: read_password_packet failed 2011-06-05 18:00:55DEBUG: pid 8147: do_md5failed in slot 0 Can any body tell my, why is the reason of this problem??? thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] About insert_lock = true
Tatsuo thank you very much for your answer.
Regards.
De: Tatsuo Ishii [is...@sraoss.co.jp]
Enviado el: domingo, 05 de junio de 2011 20:13
Para: Lazaro Rubén García Martinez
CC: pgpool-general@pgfoundry.org
Asunto: Re: [Pgpool-general] About insert_lock = true
> Hello every one in the list, I have a question related with insert_lock
> property. In the documentation says that if insert_lock is set to true
> pgpool-II automatically adds the next queries each time an INSERT is executed:
>
>
> BEGIN;
> LOCK TABLE ...
> INSERT INTO ...
> COMMIT;
>
> But in postgresql logs file, I don't see a lock table statement. The logs
> writing in postgresql logs file are:
>From the document:
pgpool-II 3.0 or later uses a row lock against the sequence
relation, rather than table lock. This will minimize lock
conflict with VACUUM (including autovacuum).
So you see "SELECT 1 FROM prueba_id_seq FOR UPDATE" instead of LOCK TABLE...
> 2011-06-05 16:59:16 VET [18284]: [3-1] LOG: statement: BEGIN
> 2011-06-05 16:59:16 VET [18284]: [4-1] LOG: duration: 0.162 ms
> 2011-06-05 16:59:16 VET [18284]: [5-1] LOG: statement: SELECT 1 FROM
> prueba_id_seq FOR UPDATE
> 2011-06-05 16:59:16 VET [18284]: [6-1] LOG: duration: 0.771 ms
> 2011-06-05 16:59:16 VET [18284]: [7-1] LOG: statement: INSERT INTO
> prueba(nombre) VALUES('Ire');
> 2011-06-05 16:59:16 VET [18284]: [8-1] LOG: duration: 0.681 ms
> 2011-06-05 16:59:16 VET [18284]: [9-1] LOG: statement: COMMIT
>
> This is an expected behavior?? I'm using pgpool-3.0.4 with postgresql 8.3.14
Yes.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] About insert_lock = true
Hello every one in the list, I have a question related with insert_lock
property. In the documentation says that if insert_lock is set to true
pgpool-II automatically adds the next queries each time an INSERT is executed:
BEGIN;
LOCK TABLE ...
INSERT INTO ...
COMMIT;
But in postgresql logs file, I don't see a lock table statement. The logs
writing in postgresql logs file are:
2011-06-05 16:59:16 VET [18284]: [3-1] LOG: statement: BEGIN
2011-06-05 16:59:16 VET [18284]: [4-1] LOG: duration: 0.162 ms
2011-06-05 16:59:16 VET [18284]: [5-1] LOG: statement: SELECT 1 FROM
prueba_id_seq FOR UPDATE
2011-06-05 16:59:16 VET [18284]: [6-1] LOG: duration: 0.771 ms
2011-06-05 16:59:16 VET [18284]: [7-1] LOG: statement: INSERT INTO
prueba(nombre) VALUES('Ire');
2011-06-05 16:59:16 VET [18284]: [8-1] LOG: duration: 0.681 ms
2011-06-05 16:59:16 VET [18284]: [9-1] LOG: statement: COMMIT
This is an expected behavior?? I'm using pgpool-3.0.4 with postgresql 8.3.14
Thank you very much for your time.
Regards.
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Error during md5 authentication
Hello, every one in the list, When a try to connect to postgresql servers through pgpool-II using md5 authetication method, in pgpool-II log file, this error is shown: trying md5 authentication 2011-06-05 18:00:55DEBUG: pid 8147: read_password_packet_password: failed to read password packet "p" 2011-06-05 18:00:55ERROR: pid 8147: do_md5: read_password_packet failed 2011-06-05 18:00:55DEBUG: pid 8147: do_md5failed in slot 0 Can any body tell my, why is the reason of this problem??? thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] Error during online recovery with pgpool!!!
Hello every one in the list, in many moments when I execute an online recovery
with pgpool, the process of online recovery works well, but in the PostgreSQL
log file, of the server that I need to recover there are many error lines. If
the process for recovering a node works well, why are there in PostgreSQL log
file, error lines?
The base-backup script used in first stage of recovery is this:
#!/bin/sh
DATA=$1
RECOVERY_TARGET=$2
RECOVERY_DATA=$3
SSH=/usr/bin/ssh
RSYNC="/usr/bin/rsync -arz --rsh=$SSH --delete"
SCP=/usr/bin/scp
PGENGINE=/usr/bin
PGCTL=$PGENGINE/pg_ctl
SED=/bin/sed
PSQL=/usr/bin/psql
PGCONF="postgresql.conf"
PGCONFTMP=/media/pgsql
PGSQLPATH=/media/pgsql
mkdir $PGSQLPATH/prueba
$SED -r -e "s/\s*archive_command\s*=.*/archive_command = '\/bin\/cp %p
\/media\/pgsql\/pg_xlog_archive\/%f'/" $RECOVERY_DATA/$PGCONF >
$PGSQLPATH/prueba/$PGCONF
chmod 644 $PGSQLPATH/prueba/$PGCONF
mv --force $PGSQLPATH/prueba/$PGCONF $RECOVERY_DATA/
rm -Rf $PGSQLPATH/prueba
$PGCTL reload -D $RECOVERY_DATA -s > /dev/null
psql -c "select pg_start_backup('pgpool-recovery')" postgres
echo "restore_command = '$RSYNC 10.13.4.181:/media/pgsql/pg_xlog_archive/%f
%p'" > /media/pgsql/data/recovery.conf
$RSYNC $DATA/base/ $RECOVERY_TARGET:$RECOVERY_DATA/base/
$RSYNC $DATA/global/ $RECOVERY_TARGET:$RECOVERY_DATA/global/
$RSYNC $DATA/pg_clog/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_clog/
$RSYNC $DATA/pg_multixact/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_multixact/
$RSYNC $DATA/pg_subtrans/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_subtrans/
$RSYNC $DATA/pg_tblspc/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_tblspc/
$RSYNC $DATA/pg_twophase/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_twophase/
$RSYNC $DATA/pg_xlog/ $RECOVERY_TARGET:$RECOVERY_DATA/pg_xlog/
psql -c "select pg_stop_backup()" postgres
$RSYNC $DATA/recovery.conf $RECOVERY_TARGET:$RECOVERY_DATA/
rm $DATA/recovery.conf
exit 0
The pgpol_recovery_pitr script used in second stage of recovery is this:
#! /bin/sh
# Online recovery 2nd stage script
#
datadir=$1 # master dabatase cluster
DEST=$2 # hostname of the DB node to be recovered
DESTDIR=$3 # database cluster of the DB node to be recovered
#port=5432 # PostgreSQL port number
archdir=/media/pgsql/pg_xlog_archive# archive log directory
# Force to flush current value of sequences to xlog
psql -U postgres -t -c 'SELECT datname FROM pg_database WHERE NOT datistemplate
AND datallowconn' template1|
while read i
do
if [ "$i" != "" ];then
psql -U postgres -c "SELECT setval(oid, nextval(oid)) FROM pg_class WHERE
relkind = 'S'" $i
fi
done
psql -U postgres -c "SELECT pgpool_switch_xlog('$archdir')" template1
PGENGINE=/usr/bin
PGCTL=$PGENGINE/pg_ctl
SED=/bin/sed
PSQL=/usr/bin/psql
PGCONF="postgresql.conf"
PGCONFTMP=/media/pgsql
PGSQLPATH=/media/pgsql
mkdir $PGSQLPATH/prueba
$SED -r -e "s/\s*archive_command\s*=.*/archive_command = 'exit 0'/"
$DESTDIR/$PGCONF > $PGSQLPATH/prueba/$PGCONF
chmod 644 $PGSQLPATH/prueba/$PGCONF
mv --force $PGSQLPATH/prueba/$PGCONF $DESTDIR/
rm -Rf $PGSQLPATH/prueba
$PGCTL reload -D $DESTDIR -s > /dev/null
The PostgreSQL log file is this:
LOG: database system was interrupted; last known up at 2011-05-25 00:02:39 VET
LOG: starting archive recovery
LOG: restore_command = '/usr/bin/rsync -arz --rsh=/usr/bin/ssh --delete
10.13.4.181:/media/pgsql/pg_xlog_archive/%f %p'
rsync: link_stat "/media/pgsql/pg_xlog_archive/0001.history" failed: No
such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1298)
[receiver=2.6.8]
FATAL: the database system is starting up
LOG: restored log file "00010007" from archive
LOG: automatic recovery in progress
FATAL: the database system is starting up
LOG: redo starts at 0/760
FATAL: the database system is starting up
LOG: restored log file "00010008" from archive
FATAL: the database system is starting up
rsync: link_stat "/media/pgsql/pg_xlog_archive/00010009"
failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1298)
[receiver=2.6.8]
LOG: could not open file "pg_xlog/00010009" (log file 0,
segment 9): No existe el fichero o el directorio
LOG: redo done at 0/860
FATAL: the database system is starting up
LOG: restored log file "00010008" from archive
rsync: link_stat "/media/pgsql/pg_xlog_archive/0002.history" failed: No
such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1298)
[receiver=2.6.8]
LOG: selected new timeline ID: 2
rsync: link_stat "/media/pgsql/pg_xlog_archive/0001.history" failed: No
such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1298)
[receiver=2.6.8]
FATAL: the database system is starting up
FATAL: the database system is starting up
LOG: arch
Re: [Pgpool-general] pgpool build dependencies
If you are using CentOS, just install these packages from its repositories. openssl-devel and krb5-devel Regards De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Sandeep Thakkar [sandee...@yahoo.com] Enviado el: jueves, 26 de mayo de 2011 8:46 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] pgpool build dependencies I have got the pgpool-II sources for version 3.0.3 and I want to build it. I see that it has dependencies on "openssl" and "krb5" libraries. But I cannot see in the doc which versions of these two libraries are required. Please help. Thanks, Sandeep ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] About SSL conections with pgpool!!!
Hello everyone in the list. I have a doubt about the configuration for using SSL with Pgpool-II. In the documentation says that: ssl_key The path to the private key file to use for incoming frontend connections. There is no default value for this option, and if left unset SSL will be disabled for incoming frontend connections. ssl_cert The path to the public x509 certificate file to use for incoming frontend connections. There is no default value for this option, and if left unset SSL will be disabled for incoming frontend connections. This path is the data directory of postgresql server, where there is a server.key and a server.cert ? Or is necesary generate a ssl_key and a ssl_cert for pgpool-II. Another question, what is the maximun number for the parameter max_pool?? Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] About load balancing!!!
Thank you very much for your answer. Regards De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Erwan [e...@antelink.com] Enviado el: viernes, 20 de mayo de 2011 11:36 Para: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About load balancing!!! Hi Lazaro On 05/20/2011 05:34 PM, Lazaro Rubén García Martinez wrote: > Tatsuo, thank you very much for your answer, I read some topics about this > and I found the answer. One question. Backend_weight is a probabilistic > number from 0 to 1?? You can use any integers you want, then pgpool-II will compute the "load balancing" ratio for each of your backend nodes. E.g: Imagine I have the following settings in my pgpool-II conf: ... backend_hostname0 = 'node-main' backend_port0 = 5432 backend_weight0 = 1000 backend_hostname1 = 'node-rescue' backend_port1 = 5432 backend_weight1 = 1 ... After restarted pgpool-II, you will be able to check the "load balancing" ratio thanks to the pcp commands: $ pcp_node_info 10 127.0.0.1 9898 login password 1 node-rescue 5432 1 0.000999 $ pcp_node_info 10 127.0.0.1 9898 login password 0 node-main 5432 2 0.999001 So here, 99% of the requests will be executed on 'node-main' (theoretically). Hope this will help. /Erwan > Thank you very much for your time. > Regards. > > De: Tatsuo Ishii [is...@sraoss.co.jp] > Enviado el: martes, 17 de mayo de 2011 4:50 > Para: Lazaro Rubén García Martinez > CC: pgpool-general@pgfoundry.org > Asunto: Re: [Pgpool-general] About load balancing!!! > > It's precisely explained in the pgpool-II document. Have you read it? > Especially figures? > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese: http://www.sraoss.co.jp > >> Hello every one in the list, Recently I need to make a presentation in my >> work about replication solutions for PostgreSQL, and I need to know how >> works the algoritms for making load balancing in Pgpool-II. This answer is >> very important for my. >> >> Thank you very much for your time. >> Regards. >> ___ >> 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 ___ 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
Re: [Pgpool-general] Error: pool_add_sent_message: portal "" already exists
Tatsuo is posible that you can send my the tar ball too, through this email address lazaro3...@gmail.com. Regards and Sorry for send many emails at the same time. De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: martes, 17 de mayo de 2011 12:48 Para: jlreg...@gmail.com CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] Error: pool_add_sent_message: portal "" already exists I will send you the tar ball via private email. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > That would be great, I'd prefer that over running 3.1 alpha2 in > production. > > Thanks for the quick responses. > > On 5/17/2011 11:19 AM, Tatsuo Ishii wrote: >> I can extract a tar ball of 3.0-STABLE from CVS for you. Does this >> help you? >> I do not recommend to use alpha version for a production system. >> -- >> Tatsuo Ishii >> SRA OSS, Inc. Japan >> English: http://www.sraoss.co.jp/index_en.php >> Japanese: http://www.sraoss.co.jp >> >>> Hi Tatsuo, >>> >>> I am running 3.0.3-2 at the moment. That could be an option, however >>> I do not have experience with CVS. Do you anticipate that there will >>> be another stable package released in the 3.0.X series? If not, is it >>> worth trying 3.1 alpha2? This is for a production cluster that we >>> hope to go live with in the next few days. >>> >>> Thanks, >>> >>> Jonathan >>> >>> >>> On 5/17/2011 5:23 AM, Tatsuo Ishii wrote: I'm not sure what pgool-II version you are using but if you are using 3.0.x, you might want to try the lastest pgpool-II-3.0-STABLE tree from the source repository. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hi everyone, > > I'm looking for help (and hopefully a solution) involving an error I > am getting while using PGPool2 in master/slave +LB mode on top of PG9 > in streaming replication mode. In general Pgpool2 is working great, > but as noted in the subject every so often we get portal errors back > from PGPool2 that result in internal server errors. When our > application is connected directly to PG9, these errors do not occur. > Digging deeper these errors seem to commonly occur in PGPool2 while in > Load Balance mode, but only sometimes are they reported back to DBI as > an error. Here is an excerpt from Pgpool2's debug log. > > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9083: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9080: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9082: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9085: pool_add_sent_message: portal "" already exists > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9085: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9078: pool_add_sent_message: portal "" already exists > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9051: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9078: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9080: pool_add_sent_message: portal "" already exists > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 9080: Execute: portal name<> > May 13 21:13:22 ip-10-119-14-100 pgpool: 2011-05-13 21:13:22 DEBUG: > pid 8910: pool_add_sent_message: portal "" already exists > > On occasion Pgpool2 logs this error at the LOG level in addition to > the DEBUG level: > > May 13 20:39:12 web2 pgpool: 2011-05-13 20:39:12 LOG: pid 8107: > pool_send_and_wait: Error or notice message from backend: : DB node > id: 0 backend pid: 8157 statement: P message: portal "" does not exist > > And when that happens our application receives the error too (And > generates an Internal server error) > > This is the error as logged by apache2, which would have originated > from DBI and DBD::Pg: > > [Fri May 13 20:39:152011] -e: DBD::Pg::st execute failed: ERROR: > portal "" does not exist at /home/www/directory_to_module/a_module.pm > line 514. > > What I'm looking for is insight into what this error means, and help > determing whether this is user error in our configuration or usage of > PGPool2, or a potential bug in PGPool2. I'd like to note in case it > helps, that when Load balancing is turned off, all portal errors go > away. However, in
Re: [Pgpool-general] About load balancing!!!
Tatsuo, thank you very much for your answer, I read some topics about this and I found the answer. One question. Backend_weight is a probabilistic number from 0 to 1?? Thank you very much for your time. Regards. De: Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: martes, 17 de mayo de 2011 4:50 Para: Lazaro Rubén García Martinez CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] About load balancing!!! It's precisely explained in the pgpool-II document. Have you read it? Especially figures? -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hello every one in the list, Recently I need to make a presentation in my > work about replication solutions for PostgreSQL, and I need to know how works > the algoritms for making load balancing in Pgpool-II. This answer is very > important for my. > > Thank you very much for your time. > Regards. > ___ > 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
Re: [Pgpool-general] pgpool-II load balancing
I read the post send by you in the email shown below, but I have a doubt. The number for backend_wheight is a number between 0 and 1?. Is this a probabilistic number? Regards. De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: viernes, 06 de mayo de 2011 18:45 Para: pgpool-general@pgfoundry.org Asunto: [Pgpool-general] pgpool-II load balancing I got a personal mail regarding pgpool-II 3.0.3 load balancing(replication mode). To share info among community, I post this. >> I may have to throw away pgool-II, unfortunately. Here is my story - >> http://mwrynn.blogspot.com/2011/05/pgpool-ii-load-balancing.html - do >> you have any advice on what I might be doing wrong? I have tested 3.0.3 by using pgbench and see no problem. 1. Make sure that pgpool-II write logs to somewhere. For example: pgpool -n ... >&/tmp/pgpool.log& Please note that "-n" is mandatory. 2. Run pgbench to issue trivial SELECTs via pgpool-II. pgbench -p -n -S -C -c 2 -t 1000 test 3. Grep pgpool log to find how many SELECTs being sent to each PostgreSQL. grep SELECT /tmp/pgpool.log|grep "node id: 0"|wc# number of queries sent to DB 0 grep SELECT /tmp/pgpool.log|grep "node id: 1"|wc# number of queries sent to DB 1 I see almost same number of quries being sent to each node. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp ___ 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
[Pgpool-general] About SSL conections with pgpool!!!
Hello everyone in the list. I have a doubt about the configuration for using SSL with Pgpool-II. In the documentation says that: ssl_key The path to the private key file to use for incoming frontend connections. There is no default value for this option, and if left unset SSL will be disabled for incoming frontend connections. ssl_cert The path to the public x509 certificate file to use for incoming frontend connections. There is no default value for this option, and if left unset SSL will be disabled for incoming frontend connections. This path is the data directory of postgresql server, where there is a server.key and a server.cert ? Or is necesary generate a ssl_key and a ssl_cert for pgpool-II. Another question, what is the maximun number for the parameter max_pool?? The number for backend_weight, is a number form 0 to 1, or it parameter can admit a number greater than 1?? Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] About load balancing!!!
Hello every one in the list, Recently I need to make a presentation in my work about replication solutions for PostgreSQL, and I need to know how works the algoritms for making load balancing in Pgpool-II. This answer is very important for my. Thank you very much for your time. Regards. ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] pgpool not working with one of the db server upgraded from 8.4.4 to 9.0.4
I think the reason of your problem is because you are using a different version of PostgreSQL in each db server. I recommend you to install the same version of PostgreSQL in your servers. Regards. De: pgpool-general-boun...@pgfoundry.org [pgpool-general-boun...@pgfoundry.org] En nombre de Tatsuo Ishii [is...@sraoss.co.jp] Enviado el: jueves, 28 de abril de 2011 19:06 Para: g...@sigmaspace.com CC: pgpool-general@pgfoundry.org Asunto: Re: [Pgpool-general] pgpool not working with one of the db server upgraded from 8.4.4 to 9.0.4 Hi, You should not mix different major version of PostgreSQL. If you upgrade master DB to 9.0.x, your problem should go away. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp > Hi, > > We are running pgpool 3.0.1 on a host with two other independent db > servers. It (psql) works for a long time with both db servers are > running postgresql 8.4.4. However, when we updated the secondary db > server to 9.0.4 yesterday, the 'psql' is not working anymore (see > below for the logs) > > I tried to disconnect the 2nd db server (9.0.4) and restart the pgpool > (in failover mode, connect to 1st db server 8.4.4), and in this case, > 'psql' has no problem. > > Is this related to postgresql 9.0.4 or something else that I did wrong > ? > > Thanks, > Gary > > -- > psql has no problem to connect directly to the 2nd db server : > > 8:46pm 309 gfu@sd3dev1:~/svn/Src/Install$ psql -h sd3db2 > psql (8.4.4, server 9.0.4) > WARNING: psql version 8.4, server version 9.0. > Some psql features might not work. > Type "help" for help. > > [sd3db2.dev1_admin].sd3dev1> > > > psql fails on pgpool connection: > > 8:56pm 310 gfu@sd3dev1:~/svn/Src/Install$ psql > psql: server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > 8:56pm 311 gfu@sd3dev1:~/svn/Src/Install$ > > > The pgpool starts without any error: > > [postgres@sd3dev1 gfu]$ pgpool -n -d -D > 2011-04-28 20:47:22 DEBUG: pid 19130: key: listen_addresses > 2011-04-28 20:47:22 DEBUG: pid 19130: value: '*' kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: port > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 5432 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: pcp_port > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 9898 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: socket_dir > 2011-04-28 20:47:22 DEBUG: pid 19130: value: '/var/run/pgpool-II-90' > kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: pcp_socket_dir > 2011-04-28 20:47:22 DEBUG: pid 19130: value: '/tmp' kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: backend_socket_dir > 2011-04-28 20:47:22 DEBUG: pid 19130: value: '/var/run/pgpool-II-90' > kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: pcp_timeout > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 10 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: num_init_children > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 60 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: max_pool > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 4 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: child_life_time > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 300 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: connection_life_time > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 0 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: child_max_connections > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 0 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: client_idle_limit > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 0 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: authentication_timeout > 2011-04-28 20:47:22 DEBUG: pid 19130: value: 60 kind: 2 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: logdir > 2011-04-28 20:47:22 DEBUG: pid 19130: value: '/var/log/pgpool-II' > kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: pid_file_name > 2011-04-28 20:47:22 DEBUG: pid 19130: value: > '/var/run/pgpool-II-90/pgpool.pid' kind: 4 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: replication_mode > 2011-04-28 20:47:22 DEBUG: pid 19130: value: true kind: 1 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: load_balance_mode > 2011-04-28 20:47:22 DEBUG: pid 19130: value: false kind: 1 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: > replication_stop_on_mismatch > 2011-04-28 20:47:22 DEBUG: pid 19130: value: true kind: 1 > 2011-04-28 20:47:22 DEBUG: pid 19130: replication_stop_on_mismatch: 1 > 2011-04-28 20:47:22 DEBUG: pid 19130: key: > failover_if_affected_tuples_mismatch > 2011-04-28 20:47:22 DEBUG: pid 19130: value: true kind: 1 > 2011-04-28 20:47:22 DEBUG: pid 19130: > failover_if_affected_tuples_mismatch: 1 > 2011-04-2
