[OSM-dev] renderd questions....

[Samir Faci (Dev)]

I've been using renderd / render_list to generate tiles as needed.

I usually issue one of two version of the command, based on need.


render_list -v --all -n 15  --socket=/var/run/renderd/renderd.sock
--min-zoom=0 --max-zoom=9   ## to generate all tiles.

cat expired_list | render_expired -v -n 15
--socket=/var/run/renderd/renderd.sock  --min-zoom=10 --max-zoom=13

lately it seems like I've been stuck on a expire_list, but while
debugging I've noticed occasionally stderr messages like the ones
listed below:


process: x=1272 y=2952 z=13
socket connect failed for: /var/run/renderd/renderd.sock
render: /tiles/default/13/0/0/75/248/136.meta
process: x=636 y=1476 z=12
socket connect failed for: /var/run/renderd/renderd.sock
render: /tiles/default/12/0/0/37/124/128.meta
process: x=318 y=738 z=11
socket connect failed for: /var/run/renderd/renderd.sock
socket connect failed for: /var/run/renderd/renderd.sock
socket connect failed for: /var/run/renderd/renderd.sock
socket connect failed for: /var/run/renderd/renderd.sock
socket connect failed for: /var/run/renderd/renderd.sock
render: /tiles/default/11/0/0/18/62/128.meta
process: x=159 y=369 z=10
render: /tiles/default/10/0/0/1/151/128.meta
read: x=159 y=370 z=10
process: x=1272 y=2960 z=13
render: /tiles/default/13/0/0/75/249/128.meta
process: x=636 y=1480 z=12
render: /tiles/default/12/0/0/37/124/136.meta
process: x=318 y=740 z=11
already requested
read: x=188 y=330 z=10
process: x=1504 y=2640 z=13


Usually I get those connection errors when the renderd services dies
for some unknown reason, or the postgresdb has problems.

I can most likely handle or fix the issue through a service
restart.... though I was wondering if there was a clean way to monitor
these errors.

Can I start renderd with additional logging somehow?  Or make renderd
error out if it sees this sort of errors?

Also.. if the connection to socket failed, would the tile request be
re-issued, or will it simple be ignored?

I basically want to know if these types of messages are problematic,
if so how to catch the event and address them or at the very least
notify me when they do occur.



--
Samir F.