Tile servers issue? - Solved

Hi,

Last week I’ve made a changes on http://www.openstreetmap.org/#map=16/49.6858/18.4270 (split forest and add a tag natural=scrub under power line).

When I look to the map, changes are not shown correctly. Some tiles are still old. But when I do an refresh (Ctrl+Shift+R) in Firefox, some new tiles becomes old and some old becomes new. And when I do refresh more times in the row, I even got all tiles old.

Initially I thought, that there is some issue with sync of tiles servers, but If I look to the some tile on all tile servers, after some reloads, all are old. My changes are not visible.

https://a.tile.openstreetmap.org/17/72246/44627.png
https://b.tile.openstreetmap.org/17/72246/44627.png
https://c.tile.openstreetmap.org/17/72246/44627.png

I’m not alone, some peoples on Slovak mail list noticed the same.

See technical details section in http://wiki.openstreetmap.org/wiki/Slippy_Map

And?

If I query http://tile.openstreetmap.org/17/72246/44627.png/status I get this:

=====
Tile is clean. Last rendered at Sat Jan 01 00:00:00 2000. Last accessed at Sun Jul 31 19:40:09 2016. Stored in file:///srv/tile.openstreetmap.org/tiles/default/17/16/26/174/53/0.meta

(Dates might not be accurate. Rendering time might be reset to an old date for tile expiry. Access times might not be updated on all file systems)

After some forced reloads I got: Mon Aug 01 11:02:37 2016. But later on, (on the same server) again Sat Jan 01 00:00:00 2000.

I never seen such behaviour. Previously, when tile was re-rendered, the new version was always served. But not now. And I don’t know, if this is normal or not.

I suspect this is to do with the proxies between you and the server. Whilst what you did should override proxies, you may find that one or more of the ISPs in line have very aggressive caching policies. This might be on transparent proxies.

There was an issue reported on #osm earlier today (around 17:00 GMT), allegedly fixed shortly afterwards.

hadw: I’m not using proxy. And I also tried direct https and this should be not affected by proxies or caches on route.

SomeoneElse: Thanks. It looks like it is solved now. Is the chat history stored somewhere? I would like to see detail :wink:

#osm isn’t publically archived as far as I’m aware, though I’m sure many people have a record as they’re always connected.