[Tilecache] local wms doesn't work with tc... port configuration problem?

[Christopher Schmidt]

On Wed, Jun 04, 2008 at 04:42:18AM -0700, Alessio Di Lorenzo wrote:
> 
> Hi List,
> 
> I'm having troubles displaying my local wms service in OL with tilecache.
> 
> My tilecache installation works properly (both in cgi mode and mod_python)
> if I cache tiles from any remote wms.
> The problem comes only when I try to cache tiles from my local wms
> (generated with umn-mapserver and staying on the same tilecache's computer):
> it shows pink tiles and when I right-click on one of the pink tiles choosing
> "View image" in the firefox contextual menu, I can view the following error
> instead the tile:
> 
> An error occurred: HTTP Error 404: Not Found
>   File "/var/www/tilecache/TileCache/Service.py", line 221, in
> modPythonHandler
>     host )
>   File "/var/www/tilecache/TileCache/Service.py", line 205, in
> dispatchRequest
>     return self.renderTile(tile, params.has_key('FORCE'))
>   File "/var/www/tilecache/TileCache/Service.py", line 138, in renderTile
>     data = layer.render(tile)
>   File "/var/www/tilecache/TileCache/Layer.py", line 411, in render
>     return self.renderTile(tile)
>   File "/var/www/tilecache/TileCache/Layers/WMS.py", line 29, in renderTile
>     tile.data, response = wms.fetch()
>   File "/var/www/tilecache/TileCache/Client.py", line 54, in fetch
>     response = self.client.open(urlrequest)
>   File "urllib2.py", line 387, in open
>     response = meth(req, response)
>   File "urllib2.py", line 498, in http_response
>     'http', request, response, code, msg, hdrs)
>   File "urllib2.py", line 425, in error
>     return self._call_chain(*args)
>   File "urllib2.py", line 360, in _call_chain
>     result = func(*args)
>   File "urllib2.py", line 506, in http_error_default
>     raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
> 
> It's possible this is a port configuration problem? If yes (...or if not)
> how can I solve it?

The URL that TileCache is trying to retrieve is returning a 404. Check
the apache access logs on the machine you expect to be getting hits to,
and check what URL is going into the logs, then visit that URL in a
browser to figure out why it's giving a 404. 

Regards,
-- 
Christopher Schmidt
MetaCarta