Hi

Am 24.07.2011 17:47, schrieb Tim Alder:

I try now to create the missing indexes. (The blocking is over.)

I believe it would be faster if we would stop the rendering for this

I stopped tirex:

osm@ptolemy:~$ ./bin/stop-tirex osm@ptolemy:~$ ./tirex/bin/tirex-status --short Can't connect to shared memory. Is the tirex-master running? osm@ptolemy:~$

time, but as I try it to use tirex-rendering-control, I got following error-message.

Greetings Tim

osm@ptolemy:~/tirex/bin$ ./tirex-rendering-control --stop cannot open configuration file '/etc/tirex/tirex.conf' at /home/project/o/s/m/osm/tirex/lib/vendor_perl/5.12/Tirex/Config.pm line 55.

The config-tile is not in the default location, so you need to specify its path on the command line:

./tirex/bin/tirex-rendering-control --config ./tirex/etc/tirex/ --stop

This is true for most commands.

Peter

Am 26.07.2011, 15:16 Uhr, schrieb Peter Körner osm-lists@mazdermind.de:

The indexes seem to be back up now, so I'll restart tirex with the new deployed styles.

We seem to have the following problem again: (nothing is rendered):

https://jira.toolserver.org/browse/TS-1100

Kay

Hi,

Am 26.07.2011, 15:34 Uhr, schrieb Peter Körner osm-lists@mazdermind.de:

That's normal ... we need to wait 900s (15 minutes) until the tirex-master recognizes the requests timed out and retries them.

Ah, good to know. Is that documented somewhere, just in case one other guy may become MMP OSM member and needs to restart tirex some day..? ;-)

Thanks, Kay

2011/7/26 Peter Körmer osm-lists@mazdermind.de:

Am 26.07.2011 15:47, schrieb Kay Drangmeister:

...

Ah, good to know. Is that documented somewhere, just in case one other guy may become MMP OSM member and needs to restart tirex some day..? ;-)

Don't think so. Can you tell a good place to document it?

You had sent a personal mail (in German) to the involved guys about how to deploy styles a few months ago. https://wiki.toolserver.org/view/OpenStreetMap seems like the right place to put it.

Cheers Colin

FYI:

To solve the performance problems on lower zoom level, I modify expire.rb a little bit so that we have now no fix MIN_ZOOM value. Instead the MIN_ZOOM is changing with definable probabilities. [1] (Expiring works on zoomlevel MIN_ZOOM to MAX_ZOOM).

Low zoom-levels cost us a lot and changes are often not visible.

So edits on OSM leads to expirings on higher zoom-level with a higher probability than on low levels. Areas with high mapping activities will re-render more often than death areas.

Z16-18 will expire each time. z10 will only expire with a probability of 1.5%. We can adjust this values each time.

I hope this help us if we restart the updating of the db, where this script works.

[1] random= rand() prob=[0,0,0,0,0,0,0,0,0,0.00625,0.0125,0.025,0.05,0.1,0.2,0.4,1,1,1] #probability for each zoomlevel to expire z = 18 while z > 0 if random<prob[z] mini=z end z -= 1 end MIN_ZOOM=mini