Hi Shahaf,

I have a similar setup, using log shipping.  I have noticed that this particular error message is not 
as helpful as you might want.  In fact, the log-shipper may actually want log #46 or #246.  Just not 
the one you gave it (#44).  I think the error message just gives you N+1, where N is the number of the 
log you tried to feed it.

Your log-shipped slave has a table called _shahaf_cluster.sl_archive_tracking.  It should have been 
created by the slony1_dump.sh script.  That table will contain one row, and the "at counter" (first 
field there) is the log number it ingested last.  It wants the at_counter + 1.  So, in the slavedb, 
select * from _sharaf_cluster.sl_archive_tracking;

Your slony logs should be numbered, monotonically increasing, and you should have that next log number 
in the directory where those logs live.  If you have that correct log, have you tried applying it?

Which script are you using to apply the logs, anyway?

As to how it got "off" from the correct order, I am not sure.  You'd have to check any logging 
programs you have, whose names are hopefully in the log-application script.

-Jennifer Spencer