Hi,


> Yup, that indicates that node #3 hasn't completed the failover.  It hasn't
> fully accepted the new provider.
> I'm not sure what to suggest on that.
>
>
I am certain with the same scripts (except for IP addresses) on 3 different
machines/nodes the failover worked perfectly, so that would seem to point to
something at OS level, the question is what ? :-)


>> Additionally, does anyone know how to make the slon logs contain a
>> timestamp (e.g. DEBUG2 [2009-01-14 12:12] syncThread), as I find it pretty
>> hard to follow what is going on when comparing the log files at multiple
>> nodes.
>>
> http://www.slony.info/documentation/runtime-config.html
>
> See the slon parameter log_timestamp.
>
> What I find *I* prefer is to use syslog to collect slon logs, with the
> result that the timestamps are generated by syslog.  I know our DBAs don't
> use that; your milage may vary.
>

Thanks for the tips, I will look into this tomorrow.

Cheers,

Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100114/7e8a1fc5/attachment.htm