On Fri, Jan 29, 2010 at 1:02 PM, Brad Nicholson
<bnichols at ca.afilias.info> wrote:
> On Thu, 2010-01-28 at 16:50 -0800, Tory M Blue wrote:
>> Understood, but this works in a similar configuration now. The script
>> starts by dropping the slon schema, than sets paths, listeners, than
>> sets some other information (priviledges etc). Then I start slon on
>> all nodes and things start to replicate. I've never had slon running
>> when I run this prepare script. Just wondering if it's something
>> different now that I'm trying to use a slave as the provider for a
>> query server, vs having all servers hit masternode (origin) directly.
>> That could be the issue I guess.
>
>
> Adding the cascaded replica is indeed the difference.
>
> In your first case, all the subscription are coming off node1.  The
> slonik command creates the events, but they are not processed until the
> slons are started.  When you start the slons up, the subscribe set
> events get processed, and everything works.
>
> In the second case, when you start the slons and the events get
> processed, you are processing the subscribe set event for the cascaded
> subscriber before the provider is an active subscriber itself.  This is
> what breaks.
>
> There probably should be a check in the subscribe set slonik command to
> ensure that the provider is subscribed and an active forwarder before
> accepting the event.
>
>

Thanks all, that was indeed the issue and although this is going to
require a ton of changes, at least with your help I'm passed this
hurdle.

Thanks for taking the time!

Tory