I'm trying to run a failover on a three node cluster (for testing purposes) and it doesn't seem to be working, no matter how I try it.

I've tried running the following in slonik:

node 1 admin conninfo = 'dbname=$dbname host=$host1 port=$port user=$user ';
node 2 admin conninfo = 'dbname=$dbname host=$host2 port=$port user=$user ';
node 3 admin conninfo = 'dbname=$dbname host=$host3 port=$port user=$user ';

echo 'Failing over...';

failover (id = 1, backup node = 2);
echo 'Dropping node 1...';
drop node (id = 1, event node = 2);
echo 'Failover complete';

I have also tried to (as per the "Failover With Complex Node Set" instructions) run subscribe set to update the subscription info for other nodes before failing over to node 2, but the subscribe set command fails with "could not connect to server: Connection refused" (even though none of the nodes used in the subscribe set command are the master node).  So I went back to just running failover and letting the failover function take care of subscribing nodes and junk.

The results have been ... well, they have been sort of random.  It does occasionally seem to report a successful run, but even then, node 3 usually has some incorrect information about the new structure of the cluster.  The most common ocurrance (and the only one I have logs for), though, is that I receive the following output from the above slonik commands:

>;stdin;stdin;stdin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100521/e959bfd1/attachment.htm