Обсуждение: Cannot connect to PgPool

Поиск
Список
Период
Сортировка

Cannot connect to PgPool

От
Christopher M Siwy
Дата:
I have 3 postgresql services running and I have them correctly
referenced in the pgpool.conf file.

However, I get the following error when I try to create db's to them
using the following command:
psql -p 9999 db_name

psql: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

The PgPool log when this occurs is the following:

2008-01-04 20:37:12 LOG:   pid 8670: Cannot accept() new connection.
all backends are down
2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler called
2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: call wait3
2008-01-04 20:37:12 DEBUG: pid 8663: child 8670 exits with status 256
by signal 0
2008-01-04 20:37:12 DEBUG: pid 8663: fork a new child pid 8881
2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: normally exited
2008-01-04 20:37:12 DEBUG: pid 8881: I am 8881

Re: Cannot connect to PgPool

От
Tatsuo Ishii
Дата:
Can you provide more info please?

- pgpool version(I assume it's pgpool-II since you use 3 PostgreSQL
  servers)

- pgpool.conf

Do you get the error right after start psql? Or it only happens after
you issue create database command?

Also please provide detailed log which can be obtained by using -d
(debug) option?
--
Tatsuo Ishii
SRA OSS, Inc. Japan


> I have 3 postgresql services running and I have them correctly
> referenced in the pgpool.conf file.
>
> However, I get the following error when I try to create db's to them
> using the following command:
> psql -p 9999 db_name
>
> psql: server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>
> The PgPool log when this occurs is the following:
>
> 2008-01-04 20:37:12 LOG:   pid 8670: Cannot accept() new connection.
> all backends are down
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler called
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: call wait3
> 2008-01-04 20:37:12 DEBUG: pid 8663: child 8670 exits with status 256
> by signal 0
> 2008-01-04 20:37:12 DEBUG: pid 8663: fork a new child pid 8881
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: normally exited
> 2008-01-04 20:37:12 DEBUG: pid 8881: I am 8881
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings

Re: Cannot connect to PgPool

От
"Christopher Siwy"
Дата:
I had this exact problem.  I had to in fact compile the pgpool-II source code rather than yum install pgpool-II.

On Jan 8, 2008 9:55 AM, Tatsuo Ishii < ishii@postgresql.org> wrote:
Can you provide more info please?

- pgpool version(I assume it's pgpool-II since you use 3 PostgreSQL
 servers)

- pgpool.conf

Do you get the error right after start psql? Or it only happens after
you issue create database command?

Also please provide detailed log which can be obtained by using -d
(debug) option?
--
Tatsuo Ishii
SRA OSS, Inc. Japan


> I have 3 postgresql services running and I have them correctly
> referenced in the pgpool.conf file.
>
> However, I get the following error when I try to create db's to them
> using the following command:
> psql -p 9999 db_name
>
> psql: server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
>
> The PgPool log when this occurs is the following:
>
> 2008-01-04 20:37:12 LOG:   pid 8670: Cannot accept() new connection.
> all backends are down
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler called
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: call wait3
> 2008-01-04 20:37:12 DEBUG: pid 8663: child 8670 exits with status 256
> by signal 0
> 2008-01-04 20:37:12 DEBUG: pid 8663: fork a new child pid 8881
> 2008-01-04 20:37:12 DEBUG: pid 8663: reap_handler: normally exited
> 2008-01-04 20:37:12 DEBUG: pid 8881: I am 8881
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings