I've setup the replication process using osmosis, based on the hourly diffs, and it was running fine until today. Now, it does nothing, like there wasn't anything else to update. But my database is not up-to-date, there are more than 2 months of diffs still to be applied. No errors output as well. Acessing link:Latest state.txt, I found that (as of now) the sequence number is listed as "7": #Sun Jul 14 18:02:07 UTC 2013 And it should be "7322" (as of now), as per the latest historic hourly diff link:000/007/322 #Sun Jul 14 09:02:10 UTC 2013 Am I doing something wrong? Did something changed (nothing on the osmosis documentation)? Is it a bug? The command used is: osmosis -v --rri workingDirectory=m:\OSM\osmosis\work --write-apidb-change host=myserver:myport password=password database=database user=username validateSchemaVersion=yes allowIncorrectSchemaVersion=no populateCurrentTables=yes asked 14 Jul '13, 19:16  MCPicoli closed 19 Sep '13, 21:49 |
The question has been closed for the following reason “Problem is not reproducible or outdated” by MCPicoli 19 Sep ‘13, 21:49
One Answer:
Seems to be fixed, but no one (here or on the email list) gave an explanation. Maybe some kind of "leftover" of the redaction period? answered 15 Jul '13, 00:50 MCPicoli |
For info, this is also being discussed on the dev list - http://lists.openstreetmap.org/pipermail/dev/2013-July/027168.html .