Sun Sep 17 18:03:01 PDT 2006
- Previous message: [Slony1-general] Second part "Slony stop after 9 hours"
- Next message: [Slony1-general] Second part "Slony stop after 9 hours"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Now I am using debud level 2 (slon -d 2 ....). > After some time that I init Slon, I made one insert then in the master > log > file: > > 2006-09-17 11:23:55 BRT DEBUG2 remoteWorkerThread_2: SYNC 5431 processing > 2006-09-17 11:23:55 BRT DEBUG2 remoteWorkerThread_2: no sets need syncing > for this event This sort of log entry is quite normal for a node that only originates replication sets. SYNCs will will come in from other nodes, and since there are no sets on node #2, there's no work to be done. > 2006-09-17 12:35:34 BRT ERROR remoteListenThread_2: timeout for event > selection Smells like a network outage. Since node 2 doesn't originate any sets, there's no data loss, so this doesn't necessarily indicate a problem. > 2006-09-17 11:24:03 BRT DEBUG2 syncThread: new sl_action_seq 23 - SYNC > 4663 > 2006-09-17 11:24:03 BRT DEBUG2 localListenThread: Received event 1,4663 > SYNC > Afer this log Slon don??t replicate more, and in log file I don??t have > more > register. These are the last logs. > > Cold someone help me? The logs for a subscriber node should have a LOT more in them than that. There can't possibly be just 2 lines of output in a slon log. In particular, there should be several log entries indicating the activity involved with SYNC #4663. What happens if you stop and restart the slons? I'd expect the one for node #2 to try event 4663 again, perhaps with more put in the logs.
- Previous message: [Slony1-general] Second part "Slony stop after 9 hours"
- Next message: [Slony1-general] Second part "Slony stop after 9 hours"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list