Thu Jul 3 05:10:56 PDT 2008
- Previous message: [Slony1-general] Execute script when subscriber lagging
- Next message: [Slony1-general] Repeating logging...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello world, I' trying to adding a node to replication after fail over following 12.4 from http://www.slony.info/documentation/addthings.html I've got only a master(node1)/save(node2) pair and i fail over promoting my slave to my new master Once my slons processes are killed, i perform the following steps - i drop my old database as node1 - i dump my new promoted slony1_extract_schema.sh from my new master. - i restore a new fresh database from the previous dump (with no slony "cruft") - i re-create my old node 1 using store node (cool : it creates the slony cluster schema by the way) store node (id=3D1, comment=3D'slony_cluster node 1', event node=3D2); - i restart my slons processes - i store my path on both sides using : STORE PATH (SERVER=3D1, CLIENT=3D2, CONNINFO=3D'dbname=3Dbop_v203_replic host=3Dkpncavern user=3Dpgslony port=3D5432'); STORE PATH (SERVER=3D2, CLIENT=3D1, CONNINFO=3D'dbname=3Dbop_v203_replic host=3Dkpnigloo user=3Dpgslony port=3D5432'); - i resubscribe node 2 to node 1: subscribe set (id=3D1, provider=3D2, receiver=3D1, forward=3Dyes); And ... no replication occures What's wrong (empty sl_table, sl_sequence on new node 1? ...)? What step is missing rgds, May warning or Notice logs gives a clue? The only things i see in in my logs are (sonce i restart slons) : slon1 : 2008-07-03 11:27:28 CEST [26359] CONFIG main: slon version 1.2.12 starting up 2008-07-03 11:27:28 CEST [26361] CONFIG main: local node id =3D 1 2008-07-03 11:27:28 CEST [26361] CONFIG main: launching sched_start_mainloop 2008-07-03 11:27:28 CEST [26361] CONFIG main: loading current cluster configuration 2008-07-03 11:27:28 CEST [26361] CONFIG storeNode: no_id=3D2 no_comment=3D'bop_slony_cluster subscriber node 2' 2008-07-03 11:27:28 CEST [26361] CONFIG storeSet: set_id=3D1 set_origin=3D2 set_comment=3D'slony_cluster Tables and Sequences' 2008-07-03 11:27:28 CEST [26361] WARN remoteWorker_wakeup: node 2 - no worker thread2008-07-03 11:27:28 CEST [26359] CONFIG main: slon version 1.2.12 starting up 2008-07-03 11:27:28 CEST [26361] CONFIG main: local node id =3D 1 2008-07-03 11:27:28 CEST [26361] CONFIG main: launching sched_start_mainloop 2008-07-03 11:27:28 CEST [26361] CONFIG main: loading current cluster configuration 2008-07-03 11:27:28 CEST [26361] CONFIG storeNode: no_id=3D2 no_comment=3D'slony_cluster subscriber node 2' 2008-07-03 11:27:28 CEST [26361] CONFIG storeSet: set_id=3D1 set_origin=3D2 set_comment=3D'slony_cluster Tables and Sequences' 2008-07-03 11:27:28 CEST [26361] WARN remoteWorker_wakeup: node 2 - no worker thread 2008-07-03 11:27:28 CEST [26361] CONFIG main: configuration complete - starting threads 2008-07-03 11:27:28 CEST [26361] DEBUG1 localListenThread: thread starts 2008-07-03 11:27:28 CEST [26361] CONFIG enableNode: no_id=3D2 2008-07-03 11:27:28 CEST [26361] DEBUG1 main: running scheduler mainloop 2008-07-03 11:27:28 CEST [26361] DEBUG1 remoteWorkerThread_2: thread starts 2008-07-03 11:27:28 CEST [26361] DEBUG1 cleanupThread: thread starts 2008-07-03 11:27:28 CEST [26361] DEBUG1 syncThread: thread starts 2008-07-03 11:33:10 CEST [26361] CONFIG storePath: pa_server=3D2 pa_client= =3D1 pa_conninfo=3D"dbname=3Dmydb host=3Dhost1 user=3Dpgslony port=3D5432" pa_co= nnretry=3D10 2008-07-03 11:33:10 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:33:10 CEST [26361] DEBUG1 remoteListenThread_2: thread starts 2008-07-03 11:33:10 CEST [26361] DEBUG1 remoteListenThread_2: connected to 'dbname=3Dmydb host=3Dhost2 user=3Dpgslony port=3D5432' 2008-07-03 11:33:10 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:33:10 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:33:10 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:38:35 CEST [26361] DEBUG1 cleanupThread: 0.030 seconds for cleanupEvent() 2008-07-03 11:38:35 CEST [26361] DEBUG1 cleanupThread: 0.020 seconds for delete logs 2008-07-03 11:47:53 CEST [26361] CONFIG storeSubscribe: sub_set=3D1 sub_provider=3D2 sub_forward=3D't' 2008-07-03 11:47:53 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:47:53 CEST [26361] DEBUG1 copy_set 1 2008-07-03 11:47:53 CEST [26361] DEBUG1 remoteWorkerThread_2: connected to provider DB 2008-07-03 11:47:53 CEST [26361] DEBUG1 remoteWorkerThread_2: disconnected from provider DB 2008-07-03 11:47:53 CEST [26361] DEBUG1 copy_set 1 done in 0.029 seconds 2008-07-03 11:47:53 CEST [26361] CONFIG enableSubscription: sub_set=3D1 2008-07-03 11:47:53 CEST [26361] CONFIG storeListen: li_origin=3D2 li_receiver=3D1 li_provider=3D2 2008-07-03 11:47:53 CEST [26361] DEBUG1 remoteWorkerThread_2: helper thread for provider 2 created 2008-07-03 11:47:55 CEST [26361] DEBUG1 remoteWorkerThread_2: connected to data provider 2 on 'dbname=3Dmydb host=3Dhost2 user=3Dpgslony port=3D5432' 2008-07-03 11:49:57 CEST [26361] DEBUG1 cleanupThread: 0.026 seconds for cleanupEvent() 2008-07-03 11:49:57 CEST [26361] DEBUG1 cleanupThread: 0.019 seconds for delete logs ../.. slon2 : 2008-07-03 11:27:28 CEST [26386] CONFIG main: slon version 1.2.12 starting up 2008-07-03 11:27:28 CEST [26388] CONFIG main: local node id =3D 2 2008-07-03 11:27:28 CEST [26388] CONFIG main: launching sched_start_mainloop 2008-07-03 11:27:28 CEST [26388] CONFIG main: loading current cluster configuration 2008-07-03 11:27:28 CEST [26388] CONFIG storeNode: no_id=3D1 no_comment=3D'slony_cluster node 1' 2008-07-03 11:27:28 CEST [26388] CONFIG storeSet: set_id=3D1 set_origin=3D2 set_comment=3D'slony_cluster Tables and Sequences' 2008-07-03 11:27:28 CEST [26388] CONFIG main: configuration complete - starting threads 2008-07-03 11:27:28 CEST [26388] DEBUG1 localListenThread: thread starts NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=3D25965 2008-07-03 11:27:28 CEST [26388] CONFIG enableNode: no_id=3D1 2008-07-03 11:27:28 CEST [26388] DEBUG1 main: running scheduler mainloop 2008-07-03 11:27:28 CEST [26388] DEBUG1 remoteWorkerThread_1: thread starts 2008-07-03 11:27:28 CEST [26388] DEBUG1 cleanupThread: thread starts 2008-07-03 11:27:28 CEST [26388] DEBUG1 syncThread: thread starts 2008-07-03 11:33:06 CEST [26388] CONFIG storePath: pa_server=3D1 pa_client= =3D2 pa_conninfo=3D"dbname=3Dmydb host=3Dhost1 user=3Dpgslony port=3D5432" pa_co= nnretry=3D10 2008-07-03 11:33:06 CEST [26388] CONFIG storeListen: li_origin=3D1 li_receiver=3D2 li_provider=3D1 2008-07-03 11:33:06 CEST [26388] DEBUG1 remoteListenThread_1: thread starts 2008-07-03 11:33:06 CEST [26388] DEBUG1 remoteListenThread_1: connected to 'dbname=3Dmydb host=3Dhost1 user=3Dpgslony port=3D5432' 2008-07-03 11:33:06 CEST [26388] CONFIG storeListen: li_origin=3D1 li_receiver=3D2 li_provider=3D1 2008-07-03 11:38:35 CEST [26388] DEBUG1 cleanupThread: 0.030 seconds for cleanupEvent() 2008-07-03 11:38:35 CEST [26388] DEBUG1 cleanupThread: 0.032 seconds for delete logs 2008-07-03 11:47:54 CEST [26388] CONFIG storeListen: li_origin=3D1 li_receiver=3D2 li_provider=3D1 2008-07-03 11:47:54 CEST [26388] CONFIG storeListen: li_origin=3D1 li_receiver=3D2 li_provider=3D1 NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=3D29851 CONTEXT: PL/pgSQL function "cleanupevent" line 77 at perform 2008-07-03 11:49:57 CEST [26388] DEBUG1 cleanupThread: 0.025 seconds for cleanupEvent() 2008-07-03 11:49:57 CEST [26388] DEBUG1 cleanupThread: 0.019 seconds for delete logs -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080703/= 96c168f3/attachment.htm
- Previous message: [Slony1-general] Execute script when subscriber lagging
- Next message: [Slony1-general] Repeating logging...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list