<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks, will try that. </p>
<p>But the problem is not that certain requests fail, but that after
a certain point all requests fail; the ones that I'm a 100% sure
are valid and cached in the sqlite, also all the layers fail at
that point.</p>
<p>So something trigger Mapproxy to deliver empty tiles to all the
requests, but since I don't know what causes the failure it is
also hard to trigger it.<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 23-10-19 22:06, Travis Kirstine
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALtm4h3=XaWUFijdXJFFqoRWD-73JCB+o9v=cYrj9Tv7ba35=w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hard to say what the issue is, I would test the service
using the mapproxy-util serve-develop tool in debug mode and
watch for errors.</div>
<div><br>
</div>
<div>mapproxy-util serve-develop -b <a
href="http://myserver.com:8585" moz-do-not-send="true">myserver.com:8585</a>
mapproxy.yaml --debug</div>
<div><br>
</div>
<div>Go to the demo site <a href="http://myserver.com:8585"
moz-do-not-send="true">myserver.com:8585</a> and turn on the
browsers developer tools and try to generate errors<br>
</div>
<div><br>
</div>
<div>My guess is either it failed to get the image from the WMS
or failed to write it to the mbtiles cache due to sqllite
table locking. <br>
</div>
<div><br>
</div>
<div><a
href="https://mapproxy.org/docs/nightly/configuration.html"
moz-do-not-send="true">https://mapproxy.org/docs/nightly/configuration.html</a>
see bulk_meta_tiles<br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 23 Oct 2019 at 06:01,
Steven Ottens <<a href="mailto:steven@minst.net"
moz-do-not-send="true">steven@minst.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
I've been asked to investigate why a MapProxy setup sometimes
fails to <br>
deliver tiles. It is mapproxy 1.9 on a VMware server with
windows server <br>
2012 and network attached storage. It is (obviously) not my
setup, nor <br>
well documented :( but what I can see it is running as a
windows service <br>
using cherrypy and python2.7<br>
<br>
All the layers are mbtile-caches looking at Geoserver WMS
(which runs <br>
fine) and they are usually fast and I don't see any heavy
server load, <br>
nor is it running out of memory.<br>
<br>
However every now and then mapproxy stops delivering the
actual tiles, <br>
but instead delivers within ~20ms an empty tile of 0 bytes.
The logs <br>
seem to be fine, but I'm not entirely sure where I should be
looking. <br>
Once I restart mapproxy all is fine again.<br>
<br>
So the question is what might cause mapproxy to deliver empty
tiles for <br>
valid requests, in stead of error messages/log messages?<br>
<br>
Cheers,<br>
<br>
Steven<br>
<br>
BTW. I understand upgrading to a newer version should be a
first step, <br>
but apart from the fact that I don't know (yet) how to upgrade
a windows <br>
service, I don't like to blindly upgrade the software without
<br>
understanding the root cause of the problem<br>
<br>
_______________________________________________<br>
MapProxy mailing list<br>
<a href="mailto:MapProxy@lists.osgeo.org" target="_blank"
moz-do-not-send="true">MapProxy@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/mapproxy"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/mapproxy</a></blockquote>
</div>
</blockquote>
</body>
</html>