Changes between Version 7 and Version 8 of MapServerErrors
- Timestamp:
- Jan 27, 2009, 11:12:03 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MapServerErrors
v7 v8 18 18 19 19 === No query information to decode. QUERY_STRING is set, but empty === 20 The MapServer program has been run but without information which tells it what to do.21 This is what is seen when the MapServer script is run by a web browser with no options.22 MapServer is intended to be run by a link with a URL which contains parameters to describe the desired map.20 The !MapServer program has been run but without information which tells it what to do. 21 This is what is seen when the !MapServer script is run by a web browser with no options. 22 !MapServer is intended to be run by a link with a URL which contains parameters to describe the desired map. 23 23 24 24 === msLoadMap(): Unable to access file. (/data/tutorial/example1-1.map) === … … 31 31 + The URL in the referencing .html file could be changed. 32 32 + The !DocumentRoot in the web server could be changed. 33 # (is there a single file in which to define MapServer's root?)33 # (is there a single file in which to define !MapServer's root?) 34 34 35 35 Information about file placement is in http://www.mapserver.org/utilities/manage.html … … 44 44 + /var/www/data 45 45 + /data 46 # (If the MapServer Tutorial is referring to /data, what can be changed to haveMapServer find data elsewhere?)46 # (If the !MapServer Tutorial is referring to /data, what can be changed to have !MapServer find data elsewhere?) 47 47 }}} 48 48 === 500 Internal Server Error === … … 51 51 Something went wrong. 52 52 53 o The people in charge of the MapServer installation will have to figure out the problem.53 o The people in charge of the !MapServer installation will have to figure out the problem. 54 54 o If running from a console cgi-bin/mapserv -v reports both INPUT=GDAL and INPUT=TIFF there may be a conflict due to including TIFF as well as GDAL. http://lists.gis.umn.edu/pipermail/mapserver-users/2004-March/011072.html 55 55 … … 59 59 * Is the server running on host "localhost" and accepting TCP/IP connections on port 5432? '. 60 60 61 The people in charge of the MapServer installation will have to check the .map file and database server. Email them the error and the URL which you used. The URL is probably visible at the top of your web browser as text which begins "http://...". Probably a double-click will highlight the URL, Control-C will copy it, and in your mail program you can use Control-V to paste it in.61 The people in charge of the !MapServer installation will have to check the .map file and database server. Email them the error and the URL which you used. The URL is probably visible at the top of your web browser as text which begins "http://...". Probably a double-click will highlight the URL, Control-C will copy it, and in your mail program you can use Control-V to paste it in. 62 62 63 o There are suggestions to the MapServer maintainers in the Technical Problems section under could not connect to server...63 o There are suggestions to the !MapServer maintainers in the Technical Problems section under could not connect to server... 64 64 65 65 == Technical Problems == … … 74 74 Something went wrong. 75 75 76 o As mentioned in DebuggingMapserver, the MS_ERRORFILE environment variable can be made to point to a file so as to make available MapServer errors.76 o As mentioned in DebuggingMapserver, the MS_ERRORFILE environment variable can be made to point to a file so as to make available !MapServer errors. 77 77 78 78 === mapserv: error while loading shared libraries: libXXX.so: cannot load shared object file: No such file or directory === … … 89 89 # If the DB server is on the web server machine, psql -l may show a list of databases. 90 90 # A username and password may be necessary: psql -U readonlyuser --password -l will connect as user readonlyuser (if that exists) and ask for its password. 91 # The MapServer would connect through 127.0.0.1, also called loopback: psql --host localhost -U readonlyuser --password -l91 # The !MapServer would connect through 127.0.0.1, also called loopback: psql --host localhost -U readonlyuser --password -l 92 92 o Check for errors from the web server and in syslog for PostgreSQL errors. 93 93 o If there are no errors in syslog, you may need to configure the PostgreSQL server to log errors.
