Hi,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5"><br></div></div>
Yup, that indicates that node #3 hasn't completed the failover. It hasn't fully accepted the new provider.<br>
I'm not sure what to suggest on that.<div class="im"><br></div></blockquote><div><br>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 ? :-) <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
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.<br>
</blockquote>
</div><a href="http://www.slony.info/documentation/runtime-config.html" target="_blank">http://www.slony.info/documentation/runtime-config.html</a><br>
<br>
See the slon parameter log_timestamp.<br>
<br>
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.<br></blockquote><div><br>Thanks for the tips, I will look into this tomorrow.<br>
<br>Cheers,<br><br>Andy <br></div></div><br>