I'd check that you're running the same version of Slony on all nodes.
When I got that error, it was resolved at about the same time that I
realized that Slony was quite specific about what version was used and
changed versions to get all of them to be the same.

 

I'm not sure of this, but I think that when Slony detects a version
mismatch, that it sets some node setting somewhere to -1 to force a
failure and this message comes from a later step that doesn't have
enough information to make a better error message.

 

Walter

 

From: slony1-general-bounces at lists.slony.info
[mailto:slony1-general-bounces at lists.slony.info] On Behalf Of Leon
Mergen
Sent: Sunday, December 02, 2007 11:58 AM
To: slony1-general at lists.slony.info
Subject: [Slony1-general] "node -1 not found in runtime configuration"

 

Hello,

Today, I decided on trying out slony as a replication solution, and
followed the "Replicating Your First Database" tutorial from the site.
All went well, the slony processes are running, and the processes seem
to see that pgbench is generating data, and try to sync. However, the
data is not appearing in the slave node -- after inspecting the log
files, I see this for the log of the slave node: 

2007-12-02 20:52:46 CET DEBUG1 copy_set 1
2007-12-02 20:52:46 CET ERROR remoteWorkerThread_1: node -1 not found in
runtime configuration
2007-12-02 20:52:46 CET WARN remoteWorkerThread_1: data copy for set 1
failed - sleep 60 seconds 

This seems to be the same problem as described in this post:
http://lists.slony.info/pipermail/slony1-general/2007-October/006880.htm
l 

However, no real solution was provided to this problem there, and it
doesn't seem to have anything to do with restarting any processes (i
even restarted both servers, and still have no luck). I have no idea
where that node id -1 is coming from -- anyone has any idea ? 

Thanks in advance!

Regards,

Leon Mergen

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20071203/ad5abbb1/attachment.htm