sorry i forgot attached the logs
the pgsql1.log  have the  messages of the  postgres on backend0
replicacion.log  contains the pgpool messages.

erobles wrote:
Hi!

i have the following  scenary:


0. First , i made a  copy of whole the postgres dir  the backend0  on backend1
1.  start up postgres on the backend0  (pgsql1), with port 6543
2.  keep  down postgres  on the backend1 (pgsql2), with port 6543 too.
3.  start up the pgpool on the port 5432 confiugred to replication.
4. NO  querys or  any transaction are executed

I tried  to start up postgres and  recovery   the   backend 1 executing pcp_recovery_command.

Checking  the logs ,  pgpool  recoveries   and reconnects the host ,  to veryfied that , i ran the pcp_attach_node and  i have the message node 1 is alive, is ok.

and  check the  postgres connection on port 6543 of the backend 1 and is  alive a,is ok.


But... i tried to  connect  psql through pgpool but the  psql is stucked

How can i tell to pgpool,  that reset its connections to allow  psql and requests and avoid that stuck???



by the way  i 'm using pgpool 2.2.6, because i can't compile the  later version on SCO 507 Openserver.

--
La información contenida en este correo electrónico es confidencial de Sensa Control Digital, S.A. de C.V. Está dirigido solamente a la dirección de correo señalada. El acceso a este correo electrónico por cualquier otra persona, No está autorizado. Si Ud. no es el receptor deliberado de este correo electrónico, cualquier difusión, copia o distribución está prohibida y puede ser ilegal. Si lo ha recibido por error, por favor notifique al emisor e inmediatamente bórrelo de forma permanente y destruya cualquier copia impresa.

The information in this Internet e-mail is confidential, belongs to Sensa Control Digital, S.A. de C.V. It is intended solely for the addressee(s). Access to this Internet e-mail by anyone else is unauthorized. If you are not the intended recipient of this e-mail, any disclosure, copying, or distribution of it is prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender and immediately and permanently delete it and destroy any copies of it that were printed out.
_______________________________________________
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general


--
La información contenida en este correo electrónico es confidencial de Sensa Control Digital, S.A. de C.V. Está dirigido solamente a la dirección de correo señalada. El acceso a este correo electrónico por cualquier otra persona, No está autorizado. Si Ud. no es el receptor deliberado de este correo electrónico, cualquier difusión, copia o distribución está prohibida y puede ser ilegal. Si lo ha recibido por error, por favor notifique al emisor e inmediatamente bórrelo de forma permanente y destruya cualquier copia impresa.

The information in this Internet e-mail is confidential, belongs to Sensa Control Digital, S.A. de C.V. It is intended solely for the addressee(s). Access to this Internet e-mail by anyone else is unauthorized. If you are not the intended recipient of this e-mail, any disclosure, copying, or distribution of it is prohibited and may be unlawful. If you have received this e-mail in error, please notify the sender and immediately and permanently delete it and destroy any copies of it that were printed out.
rm: /usr/local/pgsql83/data/postmaster.pid non-existent
Last   successful real login for postgres: Fri Feb 05 14:23:30 2010 on ttyp23
mesg: cannot change mode
DEBUG:  max_safe_fds = 92, usable_fds = 102, already_open = 8
LOG:  database system was shut down at 2010-02-05 16:55:22 CST
DEBUG:  checkpoint record is at 0/46DE84
DEBUG:  redo record is at 0/46DE84; shutdown TRUE
DEBUG:  next transaction ID: 0/402; next OID: 16407
DEBUG:  next MultiXactId: 1; next MultiXactOffset: 0
(525)srvdr:/ $ DEBUG:  transaction ID wrap limit is 2147484026, limited by database "template1"
LOG:  database system is ready to accept connections

(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ LOG:  connection received: host=192.168.4.99 port=3549
DEBUG:  forked new backend, pid=18605 socket=9
LOG:  connection authorized: user=postgres database=template1
LOG:  disconnection: session time: 0:00:00.019 user=postgres database=template1 host=192.168.4.99 port=3549
DEBUG:  server process (PID 18605) exited with exit code 0
LOG:  received SIGHUP, reloading configuration files
LOG:  parameter "shared_buffers" cannot be changed after server start; configuration file change ignored
LOG:  connection received: host=192.168.4.99 port=3557
LOG:  connection authorized: user=postgres database=template1

LOG:  statement: CHECKPOINT
DEBUG:  forked new backend, pid=18727 socket=9
LOG:  statement: SELECT pgpool_recovery('base_backup', 'pgsql2', '/usr/local/pgsql83/data')
DEBUG:  recovery_script: /usr/local/pgsql83/data/base_backup /usr/local/pgsql83/data pgsql2 /usr/local/pgsql83/data
LOGGER=/usr/bin/logger -i -p local0.info -t pgpool
+ /usr/bin/logger -i -p local0.info -t pgpool QWERTY 1 
SCP=/usr/bin/scp
RCP=/usr/bin/rcp -pr
PSQL=/usr/local/pgsql83/bin/psql
+ /usr/bin/basename /usr/local/pgsql83/data/base_backup 
/usr/local/pgsql83/data/base_backup: /usr/bin/basename: not found
BASENAME=
+ /usr/bin/hostname 
HOSTNAME=srvdr
+ /usr/bin/id -un 
ID=postgres
+ /usr/bin/logger -i -p local0.info -t pgpool Executing  as user postgres 
PG_HOME=/usr/local/pgsql83
SRC_DATA=/usr/local/pgsql83/data
DST_HOST=pgsql2
DST_DATA=/usr/local/pgsql83/data
+ /usr/bin/logger -i -p local0.info -t pgpool Executing  as user postgres 
+ /usr/bin/logger -i -p local0.info -t pgpool Executing pg_start_backup: /usr/local/pgsql83/data pgsql2 /usr/local/pgsql83/data 
+ /usr/local/pgsql83/bin/psql -U postgres -d postgres -c select pg_start_backup('pgpool-recovery') 
LOG:  connection received: host=192.168.4.99 port=3561
LOG:  connection authorized: user=postgres database=postgres
LOG:  statement: select pg_start_backup('pgpool-recovery')
DEBUG:  forked new backend, pid=18738 socket=9
 pg_start_backup 
-----------------
 0/46DF04
(1 row)

+ /usr/bin/logger -i -p local0.info -t pgpool Creating file recovery.conf 
LOG:  disconnection: session time: 0:00:00.335 user=postgres database=postgres host=192.168.4.99 port=3561
DEBUG:  server process (PID 18738) exited with exit code 0
+ chown -R postgres:postgres /usr/local/pgsql83/data 
+ echo restore_command = '/usr/bin/scp srvdr:/usr/local/pgsql83/pg_xlog_archive/%f %p' 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory base 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/base pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory global 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/global pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_clog 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_clog pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_multixact 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_multixact pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_subtrans 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_subtrans pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_tblspc 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_tblspc pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_twophase 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_twophase pgsql2:/usr/local/pgsql83/data 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing directory pg_xlog 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/pg_xlog pgsql2:/usr/local/pgsql83/data 
+ wait 
+ /usr/bin/logger -i -p local0.info -t pgpool Rsyncing file recovery.conf (with source deletion) 
+ /usr/bin/rcp -pr /usr/local/pgsql83/data/recovery.conf pgsql2:/usr/local/pgsql83/data 
+ rm /usr/local/pgsql83/data/recovery.conf 
+ sleep 5 

(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ + /usr/bin/logger -i -p local0.info -t pgpool Executing pg_stop_backup 
+ /usr/local/pgsql83/bin/psql -U postgres -d postgres -c select pg_stop_backup() 
LOG:  connection received: host=192.168.4.99 port=3570
LOG:  connection authorized: user=postgres database=postgres
DEBUG:  forked new backend, pid=18779 socket=9
LOG:  statement: select pg_stop_backup()
 pg_stop_backup 
----------------
 0/46DF60
(1 row)

+ exit 0 






LOG:  disconnection: session time: 0:00:00.029 user=postgres database=postgres host=192.168.4.99 port=3570
DEBUG:  server process (PID 18779) exited with exit code 0
LOG:  statement: CHECKPOINT
DEBUG:  creating and filling new WAL file
DEBUG:  done creating and filling new WAL file
LOG:  statement: SELECT pgpool_recovery('pgpool_recovery_pitr', 'pgsql2', '/usr/local/pgsql83/data')
DEBUG:  recovery_script: /usr/local/pgsql83/data/pgpool_recovery_pitr /usr/local/pgsql83/data pgsql2 /usr/local/pgsql83/data
LOG:  connection received: host=192.168.4.99 port=3572
LOG:  connection authorized: user=postgres database=postgres
LOG:  statement: SELECT pg_switch_xlog()
DEBUG:  forked new backend, pid=18784 socket=9
 pg_switch_xlog 
----------------
 0/1000078
(1 row)

LOG:  disconnection: session time: 0:00:00.019 user=postgres database=postgres host=192.168.4.99 port=3572
DEBUG:  server process (PID 18784) exited with exit code 0
LOG:  statement: SELECT pgpool_remote_start('pgsql2', '/usr/local/pgsql83/data')
DEBUG:  recovery_script: /usr/local/pgsql83/data/pgpool_remote_start pgsql2 /usr/local/pgsql83/data
LOGGER=/usr/bin/logger -i -p local0.info -t pgpool
+ [ 2 -ne 2 ] 
DEST=pgsql2
DESTDIR=/usr/local/pgsql83/data
PGCTL=/usr/local/pgsql83/bin/pg_ctl
+ echo Destino: pgsql2 
Destino: pgsql2
+ /usr/bin/logger -i -p local0.info -t pgpool Ejecutando postgres en pgsql2 
+ nohup rcmd pgsql2 -lroot /etc/rc2.d/S90pgsql83 
+ /usr/bin/logger -i -p local0.info -t pgpool Terminando de ejecutar postgres en pgsql2 
+ exit 0 
Sending output to nohup.out

(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ DEBUG:  archived transaction log file "000000010000000000000000.0046DF04.backup"

(525)srvdr:/ $ DEBUG:  archived transaction log file "000000010000000000000000"

(525)srvdr:/ $ 
(525)srvdr:/ $ DEBUG:  archived transaction log file "000000010000000000000001"

(525)srvdr:/ $ LOG:  unexpected EOF on client connection


LOG:  disconnection: session time: 0:00:19.514 user=postgres database=template1 host=192.168.4.99 port=3557
DEBUG:  server process (PID 18727) exited with exit code 0
LOG:  received SIGHUP, reloading configuration files
LOG:  parameter "shared_buffers" cannot be changed after server start; configuration file change ignored

(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 
(525)srvdr:/ $ 

(527)srvdr:/ $ 





(509)srvdr:/ $ 
(509)srvdr:/ $ 
(509)srvdr:/ $ 
(509)srvdr:/ $ 
<ii   start 2>&1 | grep -v 'ai_family not supported'
2010-02-05 16:55:54 LOG:   pid 18502: pgpool successfully started
2010-02-05 16:55:54 ERROR: pid 18502: connect_inet_domain_socket: connect() failed: Connection refused
2010-02-05 16:55:54 ERROR: pid 18502: health check failed. 1 th host pgsql2 at port 6543 is down
2010-02-05 16:55:54 LOG:   pid 18502: set 1 th backend down status
2010-02-05 16:55:54 LOG:   pid 18502: starting degeneration. shutdown host pgsql2(6543)
2010-02-05 16:55:54 LOG:   pid 18502: execute command: pgpool_failover
sh: pgpool_failover: not found
2010-02-05 16:55:54 LOG:   pid 18502: failover_handler: set new master node: 0
2010-02-05 16:55:54 LOG:   pid 18502: failover done. shutdown host pgsql2(6543)





2010-02-05 16:56:01 LOG:   pid 18604: starting recovering node 1
2010-02-05 16:56:02 LOG:   pid 18604: CHECKPOINT in the 1st stage done
2010-02-05 16:56:02 LOG:   pid 18604: starting recovery command: "SELECT pgpool_recovery('base_backup', 'pgsql2', '/usr/local/pgsql83/data')"
2010-02-05 16:56:17 LOG:   pid 18604: 1st stage is done
2010-02-05 16:56:17 LOG:   pid 18604: starting 2nd stage
2010-02-05 16:56:17 LOG:   pid 18604: all connections from clients have been closed


2010-02-05 16:56:18 LOG:   pid 18604: CHECKPOINT in the 2nd stage done
2010-02-05 16:56:18 LOG:   pid 18604: starting recovery command: "SELECT pgpool_recovery('pgpool_recovery_pitr', 'pgsql2', '/usr/local/pgsql83/data')"
2010-02-05 16:56:18 LOG:   pid 18604: recovery query: SELECT pgpool_remote_start('pgsql2', '/usr/local/pgsql83/data')
2010-02-05 16:56:21 LOG:   pid 18604: 1 node restarted
2010-02-05 16:56:21 LOG:   pid 18604: send_failback_request: fail back 1 th node request from pid 18604
2010-02-05 16:56:21 LOG:   pid 18502: starting fail back. reconnect host pgsql2(6543)
2010-02-05 16:56:21 LOG:   pid 18502: execute command: pgpool_failback
sh: pgpool_failback: not found
2010-02-05 16:56:21 LOG:   pid 18502: failover_handler: set new master node: 0
2010-02-05 16:56:21 LOG:   pid 18502: failback done. reconnect host pgsql2(6543)
EOFError




(512)srvdr:data $ 2010-02-05 16:58:18 LOG:   pid 18911: send_failback_request: fail back 1 th node request from pid 18911
2010-02-05 16:58:18 ERROR: pid 18911: send_failback_request: node 1 is alive.







2010-02-05 16:58:26 LOG:   pid 18911: send_failback_request: fail back 1 th node request from pid 18911
2010-02-05 16:58:26 ERROR: pid 18911: send_failback_request: node 1 is alive.
_______________________________________________
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general

Reply via email to