[Pgpool-general] problem with replication

[Lazaro Rubén García Martinez]

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-bounces at pgfoundry.org [mailto:pgpool-general-bounces at pgfoundry.org] En nombre de Cristina Bulfon
Enviado el: viernes, 23 de septiembre de 2011 08:58
Para: pgpool-general at 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 9999) 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 at pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general