I've done a little research on this, but haven't the time to actually  
work out a fix.

It seems like slonik gets stuck because it is waiting for one of the  
slon daemons to quit or restart successfully.  This has always been an  
issue for me, and I haven't been able to successfully get FAILOVER to  
execute.

--Richard



On Jul 27, 2009, at 1:53 PM, Tham wrote:

>
> The setup of 3 nodes (node 1 is master, node 2 is a slave that  
> replicates the
> master, and node 3 is another slave that replicates node 2). The
> corresponding subscribe commands are:
>
> subscribe set (id = 1, provider = 1, receiver = 2, forward = yes);
> subscribe set (id = 1, provider = 2, receiver = 3, forward = yes);
>
> At the point, everything is ok.
>
>> From node 2 (slave) machine, issue the following command:
>
> failover (id = 1, backup node = 2);
>
> slonik seems to be stuck (don't get the OS prompt for more than 15  
> minutes.
> after printing out the following message:
> <stdin>:8: NOTICE:  failedNode: set 1 has no other direct receivers  
> - move
> now
> <stdin>:8: NOTICE:  failedNode: set 1 has no other direct receivers  
> - move
> now
>
>
> Is this failover scenario in this configuration possible ? Any idea  
> why the
> slonik gets stuck ?
>
> Thank you,
> Tham
> -- 
> View this message in context: http://www.nabble.com/slonyI--2.0.2-failover-command-failure-tp24688067p24688067.html
> Sent from the Slony-I -- General mailing list archive at Nabble.com.
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general