[MapProxy] GetCapabilities request produces read data timeout in 40 seconds

[Oliver Tonnhofer]

On 27.04.2011, at 10:37, Christian Willmes wrote:
> I get an Internal Server Error 500 from Apache (MapProxy is running via
> Apache2 with mod_fcgid).
> 
> And the following appaers in the error logs:
> 
> 2011-04-27 10:24:14,706 - INFO -
> 1466:mapproxy.config.loader:load_configuration - Reading services
> configuration: /var/local/mapproxy/etc/mapproxy.yaml
> 2011-04-27 10:24:14,773 - WARNING - 1466:mapproxy.config.loader:__init__
> - unexpected key grid
> 2011-04-27 10:24:14,774 - WARNING - 1466:mapproxy.config.loader:__init__
> - unexpected key grid
> 2011-04-27 10:24:14,774 - WARNING - 1466:mapproxy.config.loader:__init__
> - unexpected key grid
> [Wed Apr 27 10:24:54 2011] [warn] mod_fcgid: read data timeout in 40 seconds
> [Wed Apr 27 10:24:54 2011] [error] [client 134.95.150.136] Premature end
> of script headers: mapproxy.fcgi, referer:
> http://<productionserver>/mapproxy/demo/
> [Wed Apr 27 10:25:05 2011] [warn] mod_fcgid: process 1466 graceful kill
> fail, sending SIGKILL
> [Wed Apr 27 10:25:11 2011] [notice] mod_fcgid: process
> /var/local/mapproxy/etc/mapproxy.fcgi(1466) exit(communication error),
> get stop signal 9


MapProxy does not respond within 40 seconds and that triggers a timeout in mod_fcgid. You could increase that timeout but a GetCapabilities request shouldn't take that long :)
Other requests work?

Do you have legends? MapProxy caches all legends with the first CapabilitieRequests to get the actual legend sizes (required for the capabilities). Maybe that server does not respond?

For the 'unexpected key grid', can you post your config?

Regards,
Oliver

-- 
Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.de
http://mapproxy.org | https://bitbucket.org/olt | @oltonn