On 5/3/2010 7:11 AM, Steve Singer wrote:
> On Mon, 3 May 2010, sowjanya v wrote:
> 
>> Hi,
> 
> How are you getting the error? Is it from the slon process or the slonik 
> process?  If it is from slonik can you send the slonik script your 
> executing, if it is from slon then can you send the slon command line + conf 
> file.
> 
> Somewhere in one of them you are referencing cluster2.

unlockSet() is executed on the origin and does not actually generate an 
event, so this must be in response to a slonik script.

However, that error message is coming from inside of getClusterStatus(), 
which is called by getLocalNodeId() in turn called by unlockSet(). Which 
means that the slony schema exists in that database, but the sequence 
sl_local_node_id has a negative value. That value is normally the 
node_id, and set during INIT CLUSTER or STORE NODE.

I think we need to know a little more about that nodes history. Like how 
was it created? How did the lockSet() work in the first place and what 
happened in the meantime?


Jan


> 
> 
>>
>> Iam getting an error as mentioned below. I have cluster6 which is valid at
>> this point of time and not  _sql_cluster2. so How do i delete all this
>> obsolete cluster. Please reply to this mail at  the earliest.
>>
>> PGRES_FATAL_ERROR select "_sql_cluster2".unlockSet(1);  - ERROR:  Slony-I:
>> Node is uninitialized - cluster _sql_cluster2
>>
>>
>> -- 
>> Sowjanya
>> Wipro Technologies
>>  Bangalore
>>
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general


-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin