Thanks! That worked, but I had to start up the Slon process as the script was
running. Previously when we did not have cascaded slaves, we ran the setup
scripts and then started Slon on all the servers.
Is there a right way to do it? Should you run the slon process on the
servers first and then run the slon setup script on the Master. 


melvin6925 wrote:
> 
>>subscribe set ( id = 1, provider = 1, receiver = 2, forward = yes);
>>subscribe set ( id = 1, provider = 2, receiver = 4, forward = no);
>>_EOF_
> 
>>If I comment out the last line (subscribing set 1 from 2 to 4 ), it runs
>>without error, so it recognizes set 1 if I don't have the cascaded
>>subscribe.
> 
> 
> Node 2 can not beome a provider until it finishes subscribing with Node 1.
> So you need to have a WAIT FOR EVENT (ORIGIN=1, CONFIRMED=2);
> after the 1st subscribe and before the second. 
> ie;
> 
> subscribe set ( id = 1, provider = 1, receiver = 2, forward = yes);
> WAIT FOR EVENT (ORIGIN=1, CONFIRMED=2);
> subscribe set ( id = 1, provider = 2, receiver = 4, forward = no);
> 
> Melvin Davidson 
> 
> 
> 
>       
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 
> 

-- 
View this message in context: http://old.nabble.com/Error-while-trying-to-set-up-cascaded-Slony-slave-tp27380132p27380356.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.