In this post we will see how to configure the lighttpd HTTP server to get written to its log files the activity of TileCache (version 2.10) when they communicate via the FastCGI protocol.

Finally, we see what it seems a lighttpd feature bug that prevents the TileCache debug log get written to lighttpd log file and how to override this issue.

1. TileCache logging

TileCache sends its debug output to the (standard error stream by default. This output includes information like the requested tile (its bounding box and x, y, z coords, where z represents the zoom level), time and whether it was a cache hit or cache miss. This information will be indispensable for debugging or estimating how much time the seeding of a WMS cache will last.

2. Configuring lighttpd to receive TileCache debug output

The very first step to get lighttpd receiving TileCache debug output is that TileCache generates debug output. In the TileCache configuration file the parameter debug must be set to ‘yes’ for every layer whose debug output we want to see.

[cache]
type=Disk
base=/mnt/geodata/tilecache/
 
[municipalities]
debug=yes
type=WMSLayer
url=http://myserver/sdi-lugo?service=WMS&transparent=true
extension=png
size=256,256
bbox=580000,4688000,680000,4850000
layers=municipalities
srs=EPSG:23029
extent_type=loose
maxResolution=200
levels=10

More…