> From: Christopher Browne [mailto:cbbrowne at ca.afilias.info]
> You should now see that the slons each submit _some_ events back and
> forth.  Not much, but there should be a "back and forth" of some SYNCs
> and confirmations thereof.  Hmm.  What's the default...  There may be
> just one event every minute or so per "otherwise-inactive" node.  So
> it's hardly a "world-threatening flood."  :-)

Nothing mentioning SYNC at all.

Just these when do send the appropriate commands:

CONFIG storePath: pa_server=1 pa_client=2
pa_conninfo="dbname=prod_provision host=154.8.2.50 user=slony"
pa_connretry=10

CONFIG storeListen: li_origin=1 li_receiver=2 li_provider=1


> >> >> After doing this, the nodes should start a greater "flood" of
> >> > activity.
> >
> > Both nodes started with the same db dump before any of the slony
stuff.
> > Still no sign of any floods of activity, not even a trickle :)
> >
> > Any info you'd like me to send on to aid tracking problem down?
> 
> The next step, I'd say, is to set up the replication set on the
> "master," (e.g. - CREATE SET) add in the tables that are to be
> replicated (e.g. - SET ADD TABLE) , and then submit a SUBSCRIBE SET.

On the master I get NOTICE and CONTEXT activity after the CREATE SET and
SET ADD TABLE and SET SEQUENCES.

subscribe set ( id = 1, provider = 1, receiver = 2, forward = yes );

After the SUBSCRIBE SET the slave node activity mirrors the master's
NOTICE/CONTEXT messages and also gives;

CONFIG enableSubscription: sub_set=1


..then it goes quiet. Tried doing an insert, but not a sausage

Jase