Hi Craig,

I had a similar scenario a few months ago and never managed to figure out what happened. Nobody could tell me what the node -1 was all about, I did hear that it was possibly something pgAdmin was using to manage things, or slony switching the node to -1 to prevent further operations when trying to subscribe an ID already present on the slave.

I'd love to know if you  get to the bottom of it.

I could only guess that it was for one of the following 2 reasons:

- I tried to add a table to a set by creating a new set, subscribing then merging it.

However at the time I was managing slony using pgadmin, and I presume because I didn't wait for confirmations from both nodes regarding the subscribe before preceding with the merge it shagged it. I now avoid using pgadmin for anything replication wise other than viewing and make sure I have the following in my slonik scripts between subscribe and merge.

WAIT FOR EVENT (ORIGIN=2, CONFIRMED = 1, TIMEOUT = 0);
SYNC(ID = 1);
WAIT FOR EVENT (ORIGIN = 1, CONFIRMED = 2, TIMEOUT = 0);

Imho pgAdmin should block anyone trying to merge a set before getting the relevent confirmations from the last subscribe.

- I somehow managed to assign an id already used, again using pgAdmin and it managed to shag something.

Since I've been using slonik exclusively and making sure I sync and wait for event I've not had any problems.

Glyn


----- Original Message ----
> From: Craig James <craig_james at emolecules.com>
> To: slony1-general at lists.slony.info
> Sent: Friday, 4 April, 2008 3:54:24 PM
> Subject: [Slony1-general] drop-set/create-set, causes  "node -1 not found"
> 
> A replication set failed to do the initial copy (the network connection is 
> unreliable), and got into a state where it couldn't finish.  So I did a drop-set 
> / create-set to recreate the set, using the exact same slonik commands that I 
> used initially.
> 
> Now I get an 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?  Any help would be appreciated, I REALLY need to get this 
> database copied soon!
> 
> Thanks,
> Craig
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
> 




      ___________________________________________________________ 
Yahoo! For Good helps you make a difference  

http://uk.promotions.yahoo.com/forgood/