Hello,

 

I'm trying to use the slony_logshipper tool to update a log-shipped
slave.  I kicked off the process and monitored the log file.  After a
short time, I noticed this in the log:

 

ERROR 2008-04-29 13:56:24 > PGRES_FATAL_ERROR: ERROR:  Slony-I: node is
on archive counter 44, this archive log expects 45

Query was: select "_shahaf_cluster".archiveTracking_offline('46',
'2008-04-29 13:41:46.204843');

WARN  2008-04-29 13:56:24 > waiting for resume

 

I can see the archiveTracking_offline function in the dump file I got
using slony1_dump.sh, the one I used to initialize my logshipped slave.
But I'm not familiar with the details of this replication scheme, so I'm
not sure why the archive counter would have gotten out of sync (whatever
that means).

 

Can anyone offer suggestions on how to fix this issue or how to analyze
it further?

 

Thanks,

 

--S

 

 

Shahaf Abileah | Lead Software Developer - Data Team

shahaf at redfin.com <mailto:shahaf at redfin.com>  | tel: 206.859.2869 |
cell: 206.331.2057 | www.redfin.com <http://www.redfin.com> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080429/0003e6da/attachment.htm