Mon Jul 28 12:04:47 PDT 2008
- Previous message: [Slony1-general] Bug in documentation
- Next message: [Slony1-general] A minor bug-fix left-out in version 1.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi People, I have been using Slony-I like this: A -> B -> C So, today, I create a new set between A -> B.. everything's ok. I did the subscribe_set command of the new set to replication C. But my replication C (Parent from B) get down, and begin to give me the following: 2008-07-28 15:53:40 BRT CONFIG storeNode: no_id=3D1 no_comment=3D'Node 1 - Postgres at localhost' 2008-07-28 15:53:40 BRT DEBUG2 setNodeLastEvent: no_id=3D1 event_seq=3D4425= 35 2008-07-28 15:53:40 BRT CONFIG storeNode: no_id=3D2 no_comment=3D'Node 2 - Postgres at 172.16.5.19' 2008-07-28 15:53:40 BRT DEBUG2 setNodeLastEvent: no_id=3D2 event_seq=3D87272 2008-07-28 15:53:40 BRT CONFIG storePath: pa_server=3D1 pa_client=3D3 pa_conninfo=3D"host=3Dlocalhost dbname=3DPostgres user=3Dpostgres port=3D54= 32" pa_connretry=3D10 2008-07-28 15:53:40 BRT CONFIG storePath: pa_server=3D2 pa_client=3D3 pa_conninfo=3D"host=3D172.16.5.19 dbname=3DPostgres user=3Dpostgres port=3D= 5432" pa_connretry=3D10 2008-07-28 15:53:40 BRT CONFIG storeListen: li_origin=3D2 li_receiver=3D3 li_provider=3D2 2008-07-28 15:53:40 BRT CONFIG storeListen: li_origin=3D2 li_receiver=3D3 li_provider=3D1 2008-07-28 15:53:40 BRT CONFIG storeListen: li_origin=3D1 li_receiver=3D3 li_provider=3D2 2008-07-28 15:53:40 BRT CONFIG storeSet: set_id=3D11 set_origin=3D1 set_comment=3D'Set 11 for replication_Postgres' 2008-07-28 15:53:40 BRT WARN remoteWorker_wakeup: node 1 - no worker thread 2008-07-28 15:53:40 BRT DEBUG2 sched_wakeup_node(): no_id=3D1 (0 threads + worker signaled) 2008-07-28 15:53:40 BRT CONFIG storeSet: set_id=3D12 set_origin=3D1 set_comment=3D'Set 12 for replication_Postgres' 2008-07-28 15:53:40 BRT WARN remoteWorker_wakeup: node 1 - no worker thread 2008-07-28 15:53:40 BRT DEBUG2 sched_wakeup_node(): no_id=3D1 (0 threads + worker signaled) 2008-07-28 15:53:40 BRT CONFIG storeSet: set_id=3D1 set_origin=3D1 set_comment=3D'Set 1 for replication_Postgres' 2008-07-28 15:53:41 BRT DEBUG1 syncThread: thread done 2008-07-28 15:53:41 BRT DEBUG1 localListenThread: thread done 2008-07-28 15:53:41 BRT DEBUG1 main: scheduler mainloop returned 2008-07-28 15:53:41 BRT DEBUG2 main: wait for remote threads 2008-07-28 15:53:41 BRT DEBUG2 sched_wakeup_node(): no_id=3D1 (0 threads + worker signaled) 2008-07-28 15:53:41 BRT DEBUG2 remoteListenThread_1: queue event 2,87311 SYNC 2008-07-28 15:53:41 BRT DEBUG2 remoteWorker_event: ignore new events due to shutdown 2008-07-28 15:53:41 BRT DEBUG2 remoteListenThread_1: queue event 2,87312 SYNC 2008-07-28 15:53:41 BRT DEBUG2 remoteWorker_event: ignore new events due to shutdown 2008-07-28 15:53:41 BRT DEBUG1 remoteWorkerThread_1: helper thread for provider 2 terminated 2008-07-28 15:53:41 BRT DEBUG2 remoteListenThread_1: queue event 2,87313 SYNC 2008-07-28 15:53:41 BRT DEBUG2 remoteWorker_event: ignore new events due to shutdown 2008-07-28 15:53:41 BRT DEBUG1 remoteWorkerThread_1: thread done 2008-07-28 15:53:41 BRT DEBUG2 remoteListenThread_1: queue event 2,87314 SYNC 2008-07-28 15:53:41 BRT DEBUG2 remoteWorker_event: ignore new events due to shutdown 2008-07-28 15:53:41 BRT DEBUG2 remoteListenThread_1: queue event 2,87315 SYNC 2008-07-28 15:53:41 BRT DEBUG2 remoteWorker_event: ignore new events due to shutdown Does anybody already get something like this? Tnks, People. Regards, Rafael Domiciano -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080728/= a766ea82/attachment.htm
- Previous message: [Slony1-general] Bug in documentation
- Next message: [Slony1-general] A minor bug-fix left-out in version 1.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list