[OSM-dev] Renderd problems.

[Jon Burgess]

On Fri, 2010-07-23 at 12:40 -0500, Samir Faci (Dev) wrote:
> I have renderd installed as a service.
> 
> I'm on the latest version checkout from:
> http://github.com/openstreetmap/mod_tile.git
> 
> Running on Ubuntu Lucid, 64bit.
> 
> I usually render using one of these commands:
> 
> /usr/bin/render_list -v --all -n 4
> --socket=/var/run/renderd/renderd.sock --min-zoom=0 --max-zoom=13
> 
> cat /tiles/expired_list | /usr/bin/render_expired -v -n 4
> --socket=/var/run/renderd/renderd.sock  --map=default --min-zoom=10
> --max-zoom=13
> 
> 
> While its rendering... I'd occasionally get errors communicating with
> the socket:
> 
> ie:
> send error: Broken pipe
> recv error: Broken pipe
> process: x=1512 y=692 z=11
> already requested
> read: x=655 y=434 z=10
> process: x=5240 y=3472 z=13
> render: /tiles/default/13/0/16/77/121/128.meta
> Requesting xml(default) x(5240) y(3472) z(13)
> send error: Broken pipe
> recv error: Broken pipe
> process: x=2620 y=1736 z=12
> render: /tiles/default/12/0/0/166/60/136.meta
> 
> I was wondering if anyone else has experience any problems with
> renderd?  There is no rhyme or reason.  Sometimes it would process
> 0-13 without any problems.  Sometimes it dies in the middle of a long
> process.  Sometimes it dies right away.
> 
> I'm not sure if there's a more verbose mode I can run or debug mode
> ...but I can't seem to force it to re-create this problem, though it
> does keep on re-occuring.
> 
> Oh, and if I restart it.. that fixes everything, until the next time.

The pipe errors occur when the renderd process exits. By default the
render daemon sends its output to the system log. Take a look there
first. If there is nothing obvious then run it in the foreground with:

	renderd -f

The information from when the process exits should give important clues
about the problem.

	Jon