[OSM-talk-be] Fwd: [OSM-talk] overpass-api.de: Emergency rollback
For those that do not read the talk mailing list and are involved in the AGIV/CRAB import software regards m -- Forwarded message -- From: Roland Olbricht roland.olbri...@gmx.de Date: Tue, Nov 4, 2014 at 10:37 AM Subject: Re: [OSM-talk] overpass-api.de: Emergency rollback To: OSM Talk t...@openstreetmap.org Dear all, the Overpass API instance on overpass-api.de will receive in a few hours a data rollback to 22nd Oct 2014. This means a shutdown for two to three hours. Then it will catch up from 22nd October to recent data. The server is back to normal operations. Thank you for your patience. Best regards, Roland ___ talk mailing list t...@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ Talk-be mailing list Talk-be@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-be
Re: [OSM-talk] overpass-api.de: Emergency rollback
Dear all, the Overpass API instance on overpass-api.de will receive in a few hours a data rollback to 22nd Oct 2014. This means a shutdown for two to three hours. Then it will catch up from 22nd October to recent data. The server is back to normal operations. Thank you for your patience. Best regards, Roland ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
[OSM-talk-be] Fwd: [OSM-talk] overpass-api.de: Emergency rollback
FYI: This might influence the CRAB imports . Glenn Forwarded Message Subject: [OSM-talk] overpass-api.de: Emergency rollback Date: Sun, 02 Nov 2014 21:11:36 +0100 From: Roland Olbricht roland.olbri...@gmx.de To: osm-talk t...@openstreetmap.org Dear all, the Overpass API instance on overpass-api.de will receive in a few hours a data rollback to 22nd Oct 2014. This means a shutdown for two to three hours. Then it will catch up from 22nd October to recent data. The other instances on - http://overpass.osm.rambler.ru/cgi/ - http://api.openstreetmap.fr/oapi/ aren't affected. They will continue to deliver current data. Recent attic data will not be available for some days. I'm sorry for the inconvenience. However, attic data before Oct 22nd should be consistently available also during rollback. Details about what most likely happened: On saturday morning I've made a software update to version 0.7.51. As there was no change in the database format, the change went smoothly and all indicators looked fine. However, I've wrongly configured the dispatcher for areas to also care on meta data. Once the areas dispatcher triggered the first update of areas, .i.e. a few hours later, it corrupted the meta data, in particular the *.idx files. The processes have run with dispatcher --osm-base --db-dir=/opt/ssd/v0.7.50/ --attic dispatcher --areas --db-dir=/opt/ssd/v0.7.50/ --attic They should have run with dispatcher --osm-base --db-dir=/opt/ssd/v0.7.50/ --attic dispatcher --areas --db-dir=/opt/ssd/v0.7.50/ At this point I would like to thank the people that have complained. This gives me the impression that a fast and prospectous resuce attempt is better than a lengthy investigation without meta data. Given the wrong parameter was the cause, future software versions will be protected about these kinds of wrong parameters to the possible extent. I'm sorry for the service disruption. Best regards, Roland ___ talk mailing list t...@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk ___ Talk-be mailing list Talk-be@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-be
[OSM-talk] overpass-api.de: Emergency rollback
Dear all, the Overpass API instance on overpass-api.de will receive in a few hours a data rollback to 22nd Oct 2014. This means a shutdown for two to three hours. Then it will catch up from 22nd October to recent data. The other instances on - http://overpass.osm.rambler.ru/cgi/ - http://api.openstreetmap.fr/oapi/ aren't affected. They will continue to deliver current data. Recent attic data will not be available for some days. I'm sorry for the inconvenience. However, attic data before Oct 22nd should be consistently available also during rollback. Details about what most likely happened: On saturday morning I've made a software update to version 0.7.51. As there was no change in the database format, the change went smoothly and all indicators looked fine. However, I've wrongly configured the dispatcher for areas to also care on meta data. Once the areas dispatcher triggered the first update of areas, .i.e. a few hours later, it corrupted the meta data, in particular the *.idx files. The processes have run with dispatcher --osm-base --db-dir=/opt/ssd/v0.7.50/ --attic dispatcher --areas --db-dir=/opt/ssd/v0.7.50/ --attic They should have run with dispatcher --osm-base --db-dir=/opt/ssd/v0.7.50/ --attic dispatcher --areas --db-dir=/opt/ssd/v0.7.50/ At this point I would like to thank the people that have complained. This gives me the impression that a fast and prospectous resuce attempt is better than a lengthy investigation without meta data. Given the wrong parameter was the cause, future software versions will be protected about these kinds of wrong parameters to the possible extent. I'm sorry for the service disruption. Best regards, Roland ___ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
