This section assumes you installed your mapproxy as a part of VTS Backend. If not, actual paths or commands may differ - e.g. if you are running mapproxy from command line instead of with init-script.
Mapproxy log file¶
The mapproxy log file is the best starting point whenever something goes wrong. If the mapproxy is installed as a part of VTS Backend, the file is located in
- I cannot see my resource
Mapproxy checks the resource definitions every five minutes (configurable). If you do not want to wait, you may force-update the definitions by
sudo /etc/init.d/vts-backend-mapproxy force-update
then, you should see at the end of the log file something like
Updating resources. ... Preparing <your/resource> ... Ready to serve <your/resource>
Then the resource will be ready. In case there is no
Ready to serve <your/resource>, there will be an error why your resource could not be loaded, that will give you a hint, where is the problem.
- Resource is
Ready to servebut tiles return 404/500 HTTP error
- When mapproxy prepares resource, it does not check all underlying data. Search log file for errors regarding your tiles, they will contain reason why tile generation failed. The paths you provided in resource definition may not exist or the data at that paths may be incomplete or corrupted. Check if all data preprocessing tools finished successfully.
- I fixed my resource definition but I see no change
When mapproxy initializes resource for the first time, it freezes its configuration in store located at
/var/vts/mapproxy/store. This is important in production environment and prevents accidental corruption or deletion of live resources but may it be counter-intuitive for beginners.
The resource is uniquely defined by its
idcombination. The easiest way to work around this configuration freezing is just to define a new (fixed) resource with slightly different
id. An alternative is to stop mapproxy, e.g. by
sudo /etc/init.d/vts-backend-mapproxy stop
then delete particular resource’s directory in
/var/vts/mapproxy/store(or the whole
/var/vts/mapproxy/store) and start mapproxy again.
- I cannot find my issue here
- Check the the issues on GitHub and connect with our development team.