Debugging

The goal of this document is to give some troubleshooting tips.

General

First you should add ?debug in the application URL to have all the JavaScript and stylesheets in separated non-minified files.

Using a browser-integrated debugging tool such as Firebug (for Firefox) or Chrome development tool is very useful.

In case of 500 errors have a look at the apache logs, located at /var/www/vhosts/<vhost_name>/logs/error.log. If we call a service behind a proxy, the log entry actually references the final URL. Therefore you may call the latter URL directly on the server by typing curl "<url>".

For print-related issues have a look at the logs in the /srv/tomcat/tomcat1/logs/mapfish-print.log file.

Mapserver

Sometime more information are available by using this command:

shp2img -m <mapfile> -o test.png -e <minx> <miny> <maxx> <maxy> -s <sizex> <sizey> -l <layers>

You may also activate Mapserver’s debug mode and set the log level in your mapfile by adding the following configuration:

MAP
    ...
    CONFIG "MS_ERRORFILE" "/tmp/ms_error.txt"
    DEBUG 5
    ...

More informations

PostgreSQL

In the /etc/postgresql/9.0/main/postgresql.conf configuration file you can set log_statement to all to see all the called statements. This file must be edited using the postgres user.

Reloading PostgreSQL is required so that the new configuration is taken into account:

sudo /etc/init.d/postgres reload

Logs are available in the /var/log/postgresql/postgresql-9.0-main.log file.

Table Of Contents

Previous topic

Client-side development

Next topic

Build a new release

This Page