[OSM-dev] glitch in minutely replication stream
The minutely replication stream was blocked for 12 hours due to a server problem. The broken sequence number was 834038, with 038.state.txt and 038.osc.gz being zero length files. When the replication was restarted these files were replaced with real data. Unfortunately this has caused a problem for using osmosis to fetch these changes automatically. Once the replication resumed it appears that osmosis skipped the changes in the new '038 files and downloaded '039 onwards. This affected the OSM rendering servers (Yevaud Orm) and I have forced them back to process everything from '037+ again to ensure the changes in the 038 file are rendered. Anyone else running services using the minutely diffs might need to do the same. Jon ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? Lynn (D) On 4/18/2014 12:50 PM, Jon Burgess wrote: The minutely replication stream was blocked for 12 hours due to a server problem. The broken sequence number was 834038, with 038.state.txt and 038.osc.gz being zero length files. When the replication was restarted these files were replaced with real data. Unfortunately this has caused a problem for using osmosis to fetch these changes automatically. Once the replication resumed it appears that osmosis skipped the changes in the new '038 files and downloaded '039 onwards. This affected the OSM rendering servers (Yevaud Orm) and I have forced them back to process everything from '037+ again to ensure the changes in the 038 file are rendered. Anyone else running services using the minutely diffs might need to do the same. Jon ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
From: Lynn W. Deffenbaugh (Mr) [mailto:ldeff...@homeside.to] Sent: Friday, April 18, 2014 3:13 PM To: dev@openstreetmap.org Subject: Re: [OSM-dev] glitch in minutely replication stream Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? 1. Edit crontab to stop updates. 2. Wait until all updates have stopped (i.e. osm2pgsql is no longer running) 3. Open /var/lib/mod_tile/.osmosis/state.txt in a text editor 4. Change the sequenceNumber line to read sequenceNumber=834037 5. Edit crontab to start updates Note: Untested, but should work. ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
Paul, how much diffs will be processed ? On 19 avril 2014 02:47:07 UTC+02:00, Paul Norman penor...@mac.com wrote: From: Lynn W. Deffenbaugh (Mr) [mailto:ldeff...@homeside.to] Sent: Friday, April 18, 2014 3:13 PM To: dev@openstreetmap.org Subject: Re: [OSM-dev] glitch in minutely replication stream Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? 1. Edit crontab to stop updates. 2. Wait until all updates have stopped (i.e. osm2pgsql is no longer running) 3. Open /var/lib/mod_tile/.osmosis/state.txt in a text editor 4. Change the sequenceNumber line to read sequenceNumber=834037 5. Edit crontab to start updates Note: Untested, but should work. ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
