[MapProxy] Tile Assembly 500 Error
Travis Kirstine
traviskirstine at gmail.com
Mon Jun 23 11:06:52 PDT 2014
BTW,
After upgrading to 1.6 I was encountering gunicorn worker timeout errors.
This was fixed by adding a larger --timeout parameter to the gunicorn
config
On 23 June 2014 13:52, Travis Kirstine <traviskirstine at gmail.com> wrote:
> I upgraded to 1.6 and it seems to be working
>
> Regards
>
>
> On 23 June 2014 04:27, Oliver Tonnhofer <olt at omniscale.de> wrote:
>
>> Hi,
>>
>> On 12.06.2014, at 22:08, Travis Kirstine wrote:
>> > I'm using an existing TMS service as a Tile source and then creating a
>> layer from the assembled tiles. The problem that I have is that mapproxy
>> will return a 500 error for a TMS request when a tile does not intersect
>> with my source TMS layers. Is there a way to configure a error handler at
>> the layer or cache level to pass a blank tile instead of a 500 error?
>>
>> 500 means an internal error that MapProxy didn't handled gracefully. So
>> it's either a bug in MapProxy or a misconfiguration. Can you post the whole
>> traceback from the console/error log?
>>
>>
>> Regards,
>> Oliver
>>
>> --
>> Oliver Tonnhofer | Omniscale GmbH & Co KG | http://omniscale.com
>> http://mapproxy.org | https://github.com/olt | @oltonn
>>
>>
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapproxy/attachments/20140623/e48bd9f0/attachment.html>
More information about the MapProxy
mailing list