[Qgis-user] Web-Client Pink screen and "FastCGI server closed connection" + "Premature end of script headers: qgis_mapserv.fcgi"

[Gunnar Oehmichen]

Hello Bernhard,

something odd: On a virtual machine I am using an older version just for
testing purposes (Last Commit of the developers: 
commit ea846cfccf21ec98f3ebb488cf849d99b6fadede
Author: Andreas Neumann <a.neumann at carto.n>
Date:   Mon Oct 7 12:24:52 2013 +0000
). 
On this version all projects are working fine.

>Check if the data is accessible from the server. 

logged onto the server via ssh, started QGIS-Desktop from there, started the
projects from within the projects folder in my corresponding web-client
folder. Data is displayed without problems.

>What is your data store? 

The project which is working is stored as a Postgis-Database Table on which
the server is running but accessed via (not via host = localhost, note that
I changed the actual values of parameters):

<datasource>dbname='dbname' host=gis.dienst.uni-landau.de port=5432
user='user' password='password' sslmode=disable key='id' srid=3035
type=MULTIPOLYGON table="schema"."table" (geom) sql=</datasource>

Layers in the project are some combinations of columns from this table.

GlobalOptions.js EPSG:

//EPSG projection code of your QGIS project
var authid = "EPSG:"+3857;

EPSG-Codes of working project:

<layername>Forest (t)</layername>
            <srs>
                <spatialrefsys>
                    <proj4>+proj=laea +lat_0=52 +lon_0=10 +x_0=4321000
+y_0=3210000 +ellps=GRS80 +towgs84=0,0,0,0,0,0,0 +units=m +no_defs</proj4>
                    <srsid>1000</srsid>
                    <srid>3035</srid>
                    <authid>EPSG:3035</authid>

(same for all the layers from PostGis-Table)

Furthermore project has two external raster-background layers from a wms:

           
<datasource>crs=EPSG:4326&featureCount=10&format=image/gif&layers=osm_auto:all&styles=&url=http://129.206.228.72/cached/osm?</datasource>
            <layername>Open streetmap</layername>
            <srs>
                <spatialrefsys>
                    <proj4>+proj=longlat +ellps=WGS84 +datum=WGS84
+no_defs</proj4>
                    <srsid>3452</srsid>
                    <srid>4326</srid>
                    <authid>EPSG:4326</authid>


I know this is not exactly best practice, but for this rather messy project
in terms of EPSGs the project is loading fine.

Now for the second project which is not working on the newer Web-CLient
version:

Datasource and and EPSG:

<datasource>./solardach_suedpfalz_VG_3857.shp</datasource>
            <srs>
                <spatialrefsys>
                    <proj4>+proj=merc +a=6378137 +b=6378137 +lat_ts=0.0
+lon_0=0.0 +x_0=0.0 +y_0=0 +k=1.0 +units=m +nadgrids=@null +wktext 
+no_defs</proj4>
                    <srsid>3857</srsid>
                    <srid>3857</srid>
                    <authid>EPSG:3857</authid>
                    <description>WGS 84 / Pseudo Mercator</description>
                    <projectionacronym>merc</projectionacronym>
                    <ellipsoidacronym>WGS84</ellipsoidacronym>
                    <geographicflag>false</geographicflag>

So here the datasource is actually in the same EPSG as defined in the
GlobalOptions.js. But if the problem was caused by a wrong EPSG, shouldn´t
have been the first project the one not working?

Thanks for your help,

Gunnar







--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Web-Client-Pink-screen-and-FastCGI-server-closed-connection-Premature-end-of-script-headers-qgis-map-tp5102953p5105070.html
Sent from the Quantum GIS - User mailing list archive at Nabble.com.