http://www.slony.info/bugzilla/show_bug.cgi?id=121

--- Comment #1 from Steve Singer <ssinger at ca.afilias.info> 2010-08-13 06:01:53 PDT ---
I've also observed this node -1 error on the cascaded nodes (ie node 4)
where I had log shipping running on the slon for node 3.

This was processing a ENABLE_SET message for set 1.

The remoteWorkerThread_1 logged
2010-08-12 20:19:28,859 [db4 stdout] DEBUG
info.slony.clustertest.testcoordinator.slony.SlonLauncher db4 - 2010-08-12
20:19:28 UTCDEBUG2 re
moteWorkerThread_1: Received event #1 from 5000000043 type:ENABLE_SUBSCRIPTION
2010-08-12 20:19:28,859 [db4 stdout] DEBUG
info.slony.clustertest.testcoordinator.slony.SlonLauncher db4 - 2010-08-12
20:19:28 UTCDEBUG2 re
moteWorkerThread_1: Received event #1 from 5000000043 type:ENABLE_SUBSCRIPTION

but around this time slon is also restarting with 

2010-08-12 20:18:58,536 [db4 stdout] DEBUG
info.slony.clustertest.testcoordinator.slony.SlonLauncher db4 - 2010-08-12
20:18:58 UTCWARN   se
rialization problem updating sl_archive_counter: restarting slon

I don't know if the sl_archive_counter is related or not to the node -1 issues.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.