Craig A. James wrote:
> During the initial copy, the master database had a problem and died.  
> Fair enough, usually Slony will try again.  But this time, it has gotten 
> itself into an invalid state -- see the attached log dump.
> 
> I have already copied a LOT of data, and the connection between master 
> and slave isn't reliable, so I don't want to start over.  I REALLY need 
> to get this system replicated SOON.  How can I repair this problem and 
> get Slony to continue?  For the moment, I've killed the slon(1) daemons, 
> but if I restart them, the "sequence ID 51 has already been assigned" 
> message just keeps getting repeated.

Ok, forget this question ... I did the obvious, drop-set followed by create-set, which recreated the original set using the exact same commands as the first time.

Now I get another error that makes no sense:

  remoteWorkerThread_1: node -1 not found in runtime configuration

So for some reason, it can't connect any more, but the only change was the drop-set/create-set.

I tried re-executing the store-path commands, but that makes no difference.  I also verified that the databases are both running, and that both are accessible.

What's going on here?

Thanks,
Craig