Hi,<br><br>Yup, it works for 2.0.7. Thanks. <br><br>But i tried for version 2.0.4 also, still its giving the same errors. We are little bit inclined to use version 2.0.4 as it is current version available with apt-get on debian and hence can be updated easily using apt-get. So is there any way i can make this work in the version 2.0.4 too? <br>
<br>Also, I noticed that on rebooting the machine, it does not even work when i kill the slon process started on reboot and manually start the slon process like ./slon conninfo=. <br><br>Regards<br>Dilraj Singh<br><br><div class="gmail_quote">
On Sat, Aug 6, 2011 at 8:42 AM, Steve Singer <span dir="ltr"><<a href="mailto:ssinger_pg@sympatico.ca">ssinger_pg@sympatico.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, 5 Aug 2011, Dilraj Singh wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
I am using postgresql-8.4 and slony1-1.2.0.3 and i have been able implement<br>
a 4 node replication cluster where nodes communicate successfully with each<br>
</blockquote>
<br></div>
Try upgrading to 2.0.7 and see if it fixes your problem.<br>
<br>
1) 2.0.3 has a bug (unrelated to your current issue) that isn't present in 2.0.2 or 2.0.4 so that release should be avoided<br>
<br>
2) 2.0.7 has some fixes related to recovering from dropped connections that might fix your issue, the error you paste below looks familiar.<br>
<br>
<snip><div><div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2011-08-05 09:25:40 PDTERROR remoteListenThread_3: "select con_origin,<br>
con_received, max(con_seqno) as con_seqno, max(con_timestamp) as<br>
con_timestamp from "_four_node_rep_cluster20".sl_<u></u>confirm where con_received<br>
<> 2 group by con_origin, con_received" 2011-08-05 09:25:42 PDTERROR <br>
remoteListenThread_3: "select ev_origin, ev_seqno, ev_timestamp, <br>
ev_snapshot, "pg_catalog".txid_snapshot_<u></u>xmin(ev_snapshot), <br>
"pg_catalog".txid_snapshot_<u></u>xmax(ev_snapshot), ev_type, <br>
ev_data1, ev_data2, ev_data3, ev_data4, ev_data5,<br>
ev_data6, ev_data7, ev_data8 from "_four_node_rep_cluster20".sl_<u></u>event<br>
e where (e.ev_origin = '3' and e.ev_seqno > '5000000005') or (e.ev_origin =<br>
'4' and e.ev_seqno > '5000000039') order by e.ev_origin, e.ev_seqno limit<br>
40" - no connection to the server<br>
<br>
and then the replication wont start working again till the time i reboot all<br>
the nodes. I am guessing it might be the case that the provider node gets<br>
reinitialized on rebooting thats why the replication starts again. I know<br>
slony is used for automated database replication so i was wondering whether<br>
there is any way in which i can make this work without rebooting all the<br>
nodes, which will be inconvenient if the number of nodes increase or for<br>
production server<br>
<br>
Any inputs on the above error will be greatly appreciated.<br>
<br>
Regards<br>
Dilraj Singh<br>
<br>
<br>
</blockquote>
</div></div></blockquote></div><br>