Hi everyone, a couple of days ago, one of the datasources of t...@h has changed and this might need adjustments of some peoples t...@h clients configuration.
currently there are 4 possible sources for data defined in the t...@h general.conf. The main osm api, the trapi servers, the roma servers and the xapi server. Two of these don't however currently work. xapi and roma. The actual roma servers have, as far as I know, never been updated to api 0.6 and thus have not been working since April. However, until two days ago, the URL used by t...@h clients to access ROMA (http://api1.osm.absolight.net:8080/api/0.6/) was redirected to the trapi servers and thus still gave valid and up to date data. This has changed and the redirect was removed, so the roma servers now always return "503 Service Unavailable" Similarly, xapi is currently either not available, or too slow too handle the load t...@h client would put on it. Even the main api, although available as a fall back, is not able to handle the load of t...@h. So, as far as I can tell, the only viable option for t...@h currently is trapi, which in fact is a very good option, as it can easily cope with the full t...@h load. It is in fact backed by 3 servers and so is fairly robust and performant (stats: http://api1.osm.absolight.net/haproxy?stats) Anyway, getting to the point. Although the default configuration is correctly set to use trapi for everything put prio 1 tiles, I suspect that some people have non default settings of the data source, as there is still a noticeable amount of clients trying to access the unavailable roma servers. It would be great, if everyone could check if they have defined "APIservers = " in their tilesAtHome.conf and if yes, either remove it to fall back to the defaults, or set it to not include roma or xapi, but trapi instead. thanks, Kai _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
