Fri Feb 29 01:26:28 PST 2008
- Previous message: [Slony1-general] Force cleanup of log_1/log_2
- Next message: [Slony1-general] Slony queueing sync events but not replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi All, I setup Slony to replicate between a RHEL 4 (master) and OpenSuSE 10.3 (slave). After using slonik scripts, it replicated the first 5 tables that I added. When I stop the slon daemon on both machines (using Ctrl-C) and restart it, it echoes a "SETADDTABLE error: table id 1 is already set. Cannot copy" I dropped the cluster, and created another cluster (testrepcluster). I subscribed other tables to testrepcluster and started the slon daemons before subscribing the slave to the master then it gives these logs: 2008-02-28 16:03:55 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."downloads_till_30092007" 2008-02-28 16:03:56 EST DEBUG3 remoteWorkerThread_1: table "public"."downloads_till_30092007" does not require Slony-I serial key 2008-02-28 16:03:56 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."gamescribers" 2008-02-28 16:03:56 EST DEBUG3 remoteWorkerThread_1: table "public"."gamescribers" does not require Slony-I serial key 2008-02-28 16:03:56 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."glowapcontent" 2008-02-28 16:03:57 EST DEBUG3 remoteWorkerThread_1: table "public"."glowapcontent" does not require Slony-I serial key 2008-02-28 16:03:57 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."horoscopecontent" 2008-02-28 16:03:58 EST DEBUG3 remoteWorkerThread_1: table "public"."horoscopecontent" does not require Slony-I serial key 2008-02-28 16:03:58 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."lgpintable" 2008-02-28 16:03:58 EST DEBUG3 remoteWorkerThread_1: table "public"."lgpintable" does not require Slony-I serial key 2008-02-28 16:03:58 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."mobilexpression" 2008-02-28 16:03:59 EST DEBUG3 remoteWorkerThread_1: table "public"."mobilexpression" does not require Slony-I serial key 2008-02-28 16:03:59 EST DEBUG2 remoteWorkerThread_1: prepare to copy table "public"."religioususers" 2008-02-28 16:03:59 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 19 2008-02-28 16:04:00 EST DEBUG3 remoteWorkerThread_1: table "public"."religioususers" does not require Slony-I serial key 2008-02-28 16:04:00 EST DEBUG2 remoteWorkerThread_1: all tables for set 1 found on subscriber 2008-02-28 16:04:01 EST DEBUG2 remoteWorkerThread_1: copy table "public"."downloads_till_30092007" 2008-02-28 16:04:02 EST DEBUG3 remoteWorkerThread_1: table "public"."downloads_till_30092007" does not require Slony-I serial key 2008-02-28 16:04:03 EST DEBUG2 remoteWorkerThread_1: Begin COPY of table "public"."downloads_till_30092007" 2008-02-28 16:04:03 EST DEBUG2 remoteWorkerThread_1: nodeon73 is 0 NOTICE: truncate of "public"."downloads_till_30092007" succeeded 2008-02-28 16:04:04 EST DEBUG2 remoteListenThread_1: queue event 1,29 SYNC 2008-02-28 16:04:05 EST DEBUG2 localListenThread: Received event 2,19 SYNC 2008-02-28 16:04:09 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 20 2008-02-28 16:04:11 EST DEBUG2 localListenThread: Received event 2,20 SYNC 2008-02-28 16:04:17 EST DEBUG2 remoteListenThread_1: queue event 1,30 SYNC 2008-02-28 16:04:19 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 21 2008-02-28 16:04:22 EST DEBUG2 remoteListenThread_1: queue event 1,31 SYNC 2008-02-28 16:04:23 EST DEBUG2 localListenThread: Received event 2,21 SYNC 2008-02-28 16:04:29 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 22 2008-02-28 16:04:35 EST DEBUG2 remoteListenThread_1: queue event 1,32 SYNC 2008-02-28 16:04:35 EST DEBUG2 localListenThread: Received event 2,22 SYNC 2008-02-28 16:04:40 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 23 2008-02-28 16:04:41 EST DEBUG2 localListenThread: Received event 2,23 SYNC 2008-02-28 16:04:49 EST DEBUG2 remoteListenThread_1: queue event 1,33 SYNC 2008-02-28 16:04:50 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 24 2008-02-28 16:04:53 EST DEBUG2 localListenThread: Received event 2,24 SYNC 2008-02-28 16:04:54 EST DEBUG2 remoteListenThread_1: queue event 1,34 SYNC 2008-02-28 16:05:00 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 25 2008-02-28 16:05:05 EST DEBUG2 localListenThread: Received event 2,25 SYNC 2008-02-28 16:05:06 EST DEBUG2 remoteListenThread_1: queue event 1,35 SYNC 2008-02-28 16:05:10 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 26 2008-02-28 16:05:11 EST DEBUG2 localListenThread: Received event 2,26 SYNC 2008-02-28 16:05:18 EST DEBUG2 remoteListenThread_1: queue event 1,36 SYNC 2008-02-28 16:05:20 EST DEBUG2 syncThread: new sl_action_seq 1 - SYNC 27 2008-02-28 16:05:23 EST DEBUG2 localListenThread: Received event 2,27 SYNC 2008-02-28 16:05:25 EST DEBUG2 remoteListenThread_1: queue event 1,37 SYNC The logs continue like that and there is no data in any of the tables. I stopped the daemons after leaving it throughout the night, dropped the clusters on both the master and slave. I then created another cluster, added tables different from the previous ones and then subscribed again but the same thing happens with the logs and no data in any of the tables. Does anybody know what the problem could be? Victor -- View this message in context: http://www.nabble.com/Slony-queueing-sync-events-but-not-replicating-tp15754921p15754921.html Sent from the Slony-I -- General mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080229/885a46f5/attachment.htm
- Previous message: [Slony1-general] Force cleanup of log_1/log_2
- Next message: [Slony1-general] Slony queueing sync events but not replicating
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list