Hi!

Anyone got an idea what could cause the following:

2006-10-15 16:49:00 PDT DEBUG2 remoteWorkerThread_1: SYNC 133182 processing
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: after archive_dir
2006-10-15 16:49:00 PDT DEBUG2 remoteWorkerThread_1: data provider 4 confirmed up to ev_seqno 133182 for ev_origin 1 - OK
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: after provider has event check2006-10-15 16:49:00 PDT DEBUG2 remoteWorkerThread_1: syncing set 2 with 5 table(s) from provider 1
2006-10-15 16:49:00 PDT DEBUG3 remoteWorkerThread_1: activate helper 1
2006-10-15 16:49:00 PDT DEBUG3 remoteWorkerThread_1: activate helper 4
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: num_providers_active=2
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: waiting for log data
2006-10-15 16:49:00 PDT ERROR  remoteWorkerThread_1: "declare LOG cursor for select     log_origin, log_xid, log_tableid,     log_actionseq, log_cmdtype, log_cmddata from "_revver".sl_log_1 where log_origin = 1 and (  order by log_actionseq; " PGRES_FATAL_ERROR ERROR:  syntax error at or near "order" at character 165
2006-10-15 16:49:00 PDT ERROR  remoteWorkerThread_1: "close LOG; " PGRES_FATAL_ERROR ERROR:  current transaction is aborted, commands ignored until end of transaction block
2006-10-15 16:49:00 PDT ERROR  remoteWorkerThread_1: helper 4 finished with error
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: returning lines to pool
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: waiting for log data
2006-10-15 16:49:00 PDT DEBUG3 remoteWorkerThread_1: helper 1 finished
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: returning lines to pool
2006-10-15 16:49:00 PDT DEBUG3 remoteWorkerThread_1: all helpers done.
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: changing helper 1 to IDLE
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: changing helper 4 to IDLE
2006-10-15 16:49:00 PDT DEBUG4 remoteWorkerThread_1: cleanup
2006-10-15 16:49:00 PDT ERROR  remoteWorkerThread_1: SYNC aborted

Any idea what I could look at to understand what is happening.

Interestingly, the two nodes showing this behaviour continue to generate
this error after I've dropped the nodes off the cluster.

TIA,

Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061017/db201957/attachment.bin