Tue Apr 29 16:39:20 PDT 2008
- Previous message: [Slony1-general] node is on archive counter 44, this archive log expects 45
- Next message: [Slony1-general] node is on archive counter 44, this archive log expects 45
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
Shahaf Abileah wrote:
> 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>
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
- Previous message: [Slony1-general] node is on archive counter 44, this archive log expects 45
- Next message: [Slony1-general] node is on archive counter 44, this archive log expects 45
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list