Re: recuperar nodo en estado 3

From: Miguel Angel Hernandez Moreno <miguel(dot)hdz(dot)mrn(at)gmail(dot)com>
To: Cesar Martin <cmartinp(at)gmail(dot)com>
Cc: pgsql-es-ayuda(at)postgresql(dot)org
Subject: Re: recuperar nodo en estado 3
Date: 2010-03-17 23:27:41
Message-ID: e720c2d1003171627x4ba0781cn1c4c891bd4054907@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda pgsql-general

Si ya lo hice!!

mira tengo el pgpool intalado ya me avente de forma completa el manual
de replicación que tiene postgres!! Osea el problema no es que no replique
sino que cuando hago un pcp_node_recovery, al parecer todo marcha de
maravilla, no hay problema, funciona y todo, pero a la hora de concluir me
arroja lo siguiente

LOG DE PGPOOL
2010-03-17 16:24:17 DEBUG: pid 5755: I am PCP 5755 accept fd 5
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: received PCP packet type of
service 'M'
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: salt sent to the client
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: received PCP packet type of
service 'R'
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: authentication OK
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: received PCP packet type of
service 'O'
2010-03-17 16:24:17 DEBUG: pid 5755: pcp_child: start online recovery
2010-03-17 16:24:17 LOG: pid 5755: starting recovering node 1
2010-03-17 16:24:17 DEBUG: pid 5755: exec_checkpoint: start checkpoint
2010-03-17 16:24:17 DEBUG: pid 5755: exec_checkpoint: finish checkpoint
2010-03-17 16:24:17 LOG: pid 5755: CHECKPOINT in the 1st stage done
2010-03-17 16:24:17 LOG: pid 5755: 1st stage is done
2010-03-17 16:24:17 LOG: pid 5755: starting 2nd stage
2010-03-17 16:25:50 ERROR: pid 5755: wait_connection_closed: existing
connections did not close in 90 sec.
2010-03-17 16:25:50 ERROR: pid 5755: start_recovery: timeover for waiting
connection closed
2010-03-17 16:25:50 DEBUG: pid 5755: pcp_child: received PCP packet type of
service 'X'
2010-03-17 16:25:50 DEBUG: pid 5755: pcp_child: client disconnecting. close
connection

TEMINAL EN DONDE HAGO EL REOVERY
linuxM:/usr/local/bin # pcp_recovery_node -d 10 pgsql1 9898 postgres
postgres 1
DEBUG: send: tos="R", len=46
DEBUG: recv: tos="r", len=21, data=AuthenticationOK
DEBUG: send: tos="D", len=6
DEBUG: recv: tos="e", len=20, data=recovery failed
DEBUG: command failed. reason=recovery failed
BackendError
DEBUG: send: tos="X", len=4

Pero si reinicio el PGPOOL y vuelvo a correr el recovery, no me marca
ningun problema,
e incluso me dice que esta bien y el nodo caido lo pone en estado 1
pero no me regresa los valores que deberian recuperarse

2010-03-17 16:32:33 DEBUG: pid 5979: I am PCP 5979 accept fd 5
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: received PCP packet type of
service 'M'
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: salt sent to the client
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: received PCP packet type of
service 'R'
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: authentication OK
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: received PCP packet type of
service 'O'
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: start online recovery
2010-03-17 16:32:33 LOG: pid 5979: starting recovering node 1
2010-03-17 16:32:33 DEBUG: pid 5979: exec_checkpoint: start checkpoint
2010-03-17 16:32:33 DEBUG: pid 5979: exec_checkpoint: finish checkpoint
2010-03-17 16:32:33 LOG: pid 5979: CHECKPOINT in the 1st stage done
2010-03-17 16:32:33 LOG: pid 5979: 1st stage is done
2010-03-17 16:32:33 LOG: pid 5979: starting 2nd stage
2010-03-17 16:32:33 LOG: pid 5979: all connections from clients have been
closed
2010-03-17 16:32:33 DEBUG: pid 5979: exec_checkpoint: start checkpoint
2010-03-17 16:32:33 DEBUG: pid 5979: exec_checkpoint: finish checkpoint
2010-03-17 16:32:33 LOG: pid 5979: CHECKPOINT in the 2nd stage done
2010-03-17 16:32:33 DEBUG: pid 5979: exec_remote_start: start
pgpool_remote_start
/usr/bin/logname: opción inválida -- i
Pruebe `/usr/bin/logname --help' para más información.
/usr/bin/logname: opción inválida -- i
Pruebe `/usr/bin/logname --help' para más información.
2010-03-17 16:32:33 DEBUG: pid 5979: exec_remote_start: finish
pgpool_remote_start
2010-03-17 16:32:33 LOG: pid 5979: 1 node restarted
2010-03-17 16:32:33 LOG: pid 5979: send_failback_request: fail back 1 th
node request from pid 5979
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler called
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: starting to select
new master node
2010-03-17 16:32:33 LOG: pid 5946: starting fail back. reconnect host
pgsql2(5432)
2010-03-17 16:32:33 LOG: pid 5946: execute command:
/home/postgres/data/pgpool-failback 1 pgsql2 5432 var/lib/pgsql/data 0 0
/usr/bin/logname: opción inválida -- i
Pruebe `/usr/bin/logname --help' para más información.
/usr/bin/logname: opción inválida -- i
Pruebe `/usr/bin/logname --help' para más información.
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6207
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6208
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6209
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6210
2010-03-17 16:32:33 DEBUG: pid 6208: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6211
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6212
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6213
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6214
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6215
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6216
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6217
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6218
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6219
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6220
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6221
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6222
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6223
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6224
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6225
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6226
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6227
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6228
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6229
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6230
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6231
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6232
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6233
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6234
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6235
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6236
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6237
2010-03-17 16:32:33 DEBUG: pid 5946: failover_handler: kill 6238
2010-03-17 16:32:33 LOG: pid 5946: failover_handler: set new master node:
0
2010-03-17 16:32:33 DEBUG: pid 6238: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6254: I am 6254
2010-03-17 16:32:33 DEBUG: pid 6207: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6209: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6210: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6211: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6213: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6212: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6214: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6215: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6216: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6217: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6218: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6255: I am 6255
2010-03-17 16:32:33 DEBUG: pid 6256: I am 6256
2010-03-17 16:32:33 DEBUG: pid 6219: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6257: I am 6257
2010-03-17 16:32:33 DEBUG: pid 6220: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6258: I am 6258
2010-03-17 16:32:33 DEBUG: pid 6221: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6259: I am 6259
2010-03-17 16:32:33 DEBUG: pid 6222: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6260: I am 6260
2010-03-17 16:32:33 DEBUG: pid 6223: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6261: I am 6261
2010-03-17 16:32:33 DEBUG: pid 6224: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6262: I am 6262
2010-03-17 16:32:33 DEBUG: pid 6225: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6263: I am 6263
2010-03-17 16:32:33 DEBUG: pid 6226: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6264: I am 6264
2010-03-17 16:32:33 DEBUG: pid 6227: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6265: I am 6265
2010-03-17 16:32:33 DEBUG: pid 6266: I am 6266
2010-03-17 16:32:33 DEBUG: pid 6228: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6267: I am 6267
2010-03-17 16:32:33 DEBUG: pid 6229: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6268: I am 6268
2010-03-17 16:32:33 DEBUG: pid 6230: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6269: I am 6269
2010-03-17 16:32:33 DEBUG: pid 6231: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6270: I am 6270
2010-03-17 16:32:33 DEBUG: pid 6232: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6271: I am 6271
2010-03-17 16:32:33 DEBUG: pid 6233: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6234: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6272: I am 6272
2010-03-17 16:32:33 DEBUG: pid 6235: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6273: I am 6273
2010-03-17 16:32:33 DEBUG: pid 6236: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6274: I am 6274
2010-03-17 16:32:33 DEBUG: pid 6237: child received shutdown request signal
3
2010-03-17 16:32:33 DEBUG: pid 6275: I am 6275
2010-03-17 16:32:33 DEBUG: pid 6276: I am 6276
2010-03-17 16:32:33 DEBUG: pid 6277: I am 6277
2010-03-17 16:32:33 DEBUG: pid 6278: I am 6278
2010-03-17 16:32:33 DEBUG: pid 6279: I am 6279
2010-03-17 16:32:33 DEBUG: pid 6280: I am 6280
2010-03-17 16:32:33 DEBUG: pid 6281: I am 6281
2010-03-17 16:32:33 DEBUG: pid 6282: I am 6282
2010-03-17 16:32:33 DEBUG: pid 6283: I am 6283
2010-03-17 16:32:33 DEBUG: pid 6284: I am 6284
2010-03-17 16:32:33 DEBUG: pid 6285: I am 6285
2010-03-17 16:32:33 LOG: pid 5946: failback done. reconnect host
pgsql2(5432)
2010-03-17 16:32:33 DEBUG: pid 5946: reap_handler called
2010-03-17 16:32:33 DEBUG: pid 5946: reap_handler: call wait3
2010-03-17 16:32:33 DEBUG: pid 5946: child 6207 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6208 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6209 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6210 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6211 exits with status 0
2010-03-17 16:32:33 LOG: pid 5979: recovery done
2010-03-17 16:32:33 DEBUG: pid 5946: child 6212 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6213 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6214 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6215 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6216 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6217 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6218 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6219 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6220 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6221 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6222 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6223 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6224 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6225 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6226 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6227 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6228 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6229 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6230 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6231 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6232 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6233 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6234 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6235 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6236 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6237 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: child 6238 exits with status 0
2010-03-17 16:32:33 DEBUG: pid 5946: reap_handler: normally exited
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: received PCP packet type of
service 'X'
2010-03-17 16:32:33 DEBUG: pid 5979: pcp_child: client disconnecting. close
connection

y esto es lo que me dice la terminal

linuxM:/usr/local/bin # pcp_recovery_node -d 10 pgsql1 9898 postgres
postgres 1
DEBUG: send: tos="R", len=46
DEBUG: recv: tos="r", len=21, data=AuthenticationOK
DEBUG: send: tos="D", len=6
DEBUG: recv: tos="c", len=20, data=CommandComplete
DEBUG: send: tos="X", len=4

Que pasa ahi??
que estoy haciendo mal??
por que cuando reinicio el pgpool y corro el recovery me dice que es
correcto??
que estoy haciendo mal??

bueno compañero es todo, de antemano muchas gracias que tengan bonita tarde
y si alguien puede ayudarme muchas gracias!!!

In response to

Responses

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Ing . Marcos Luís Ortíz Valmaseda 2010-03-18 02:33:33 Re: ¿logger? en script de pgool
Previous Message Miguel Angel Hernandez Moreno 2010-03-17 22:37:35 replicacion de datos con pgpool

Browse pgsql-general by date

  From Date Subject
Next Message Takahiro Itagaki 2010-03-18 03:34:20 Re: [GENERAL] trouble with to_char('L')
Previous Message Alban Hertroys 2010-03-17 23:06:03 Re: update ... set ... subquery