[pgpool-general: 2231] Re: Cannot accept() new connection. all backends are down

[Tatsuo Ishii]

1) pgpool thinks all backends down because the status file says. If
   you think PostgreSQL are all healthy, try to start pgoool with -D
   option (discard status file).

2) There are configuration mistakes which prevent from pgpool
   connecting to PostgreSQL. To find the cause, a full log from
   pgpool starts up is needed (partial log below is not useful).
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> Hi all,
> 
> I'm with a problem and have no idea how may I fix.
> 
> I'm trying to install a pgpool-II to be only a connection pool (not
> replication, master slave...), only connection pool.
> 
> When I try to connect to database directly by the port of database, it
> works, but when I try to connect by the port of a pgpool it does not
> work.
> 
> Enviorement:
> Debian 6
> Postgresql 9.3
> pgpool-II 3.3.1-1.pgdg60+1
> 
> Log:
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 LOG:   pid 10333:
> Cannot accept() new connection. all backends are down
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10284:
> reap_handler called
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10284:
> reap_handler: call wait3
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10284:
> child 10333 exits with status 256
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10284:
> fork a new child pid 10456
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10284:
> reap_handler: normally exited
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10456: I am 10456
> Nov  5 15:31:13 debpg01 pgpool: 2013-11-05 15:31:13 DEBUG: pid 10456:
> pool_initialize_private_backend_status: initialize backend status
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general