If I restart with command "kill" or with "restart node 1" (in the slonik
script) the master return the replicate.

 With command "grep -v DEBUG2   /var/lib/postgres/slon_log" I look that has
some problem with sequence, but I don?t know what I need to do.
2006-09-18 09:39:15 BRT DEBUG1 cleanupThread:    0.180 seconds for
cleanupEvent()
2006-09-18 08:27:42 BRT DEBUG1 cleanupThread: -4293.276 seconds for delete
logs
2006-09-18 09:39:15 BRT DEBUG1 cleanupThread:    0.014 seconds for
cleanupEvent()
2006-09-18 09:39:15 BRT DEBUG1 cleanupThread:    0.280 seconds for delete
logs
2006-09-18 08:55:19 BRT DEBUG1 cleanupThread: -4294.470 seconds for
cleanupEvent()
2006-09-18 08:55:19 BRT DEBUG1 cleanupThread:    0.369 seconds for delete
logs
2006-09-18 10:06:52 BRT DEBUG1 cleanupThread:    0.209 seconds for
cleanupEvent()
2006-09-18 10:06:52 BRT DEBUG1 cleanupThread:    0.066 seconds for delete
logs

*2006-09-18 11:01:26 BRT ERROR  remoteListenThread_2: timeout for event
selection
*
2006-09-18 11:01:26 BRT DEBUG1 cleanupThread:    0.127 seconds for
cleanupEvent()
2006-09-18 11:01:26 BRT DEBUG1 cleanupThread:    0.137 seconds for delete
logs
2006-09-18 10:00:53 BRT DEBUG1 cleanupThread:    0.005 seconds for
cleanupEvent()
2006-09-18 10:00:53 BRT DEBUG1 cleanupThread:    0.036 seconds for delete
logs
2006-09-18 10:13:01 BRT DEBUG1 cleanupThread:    0.021 seconds for
cleanupEvent()
2006-09-18 10:13:01 BRT DEBUG1 cleanupThread:    0.032 seconds for delete
logs
2006-09-18 10:25:10 BRT DEBUG1 cleanupThread:    0.005 seconds for
cleanupEvent()







2006/9/17, cbbrowne at ca.afilias.info <cbbrowne at ca.afilias.info>:
>
> >  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.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://gborg.postgresql.org/pipermail/slony1-general/attachments/20060918/b4f45f15/attachment-0001.html