AW: [postgis-users] MapServer and PostGIS 1 RC1 and RC2

Düster Horst Horst.Duester at bd.so.ch
Thu Jan 27 08:45:09 PST 2005


> What you can try is feeding the simplest crashing query 
> to valgrind and send a report. For example:

I tried out some separated queries with the following results:

test-# select asbinary('POINT(1 1)');
                                    asbinary
----------------------------------------------------------------------------
----
 
\001\001\000\000\000\000\000\000\000\000\000\360?\000\000\000\000\000\000\36
0?

test-# select force_2d(asbinary('POINT(1 1)'));
                  force_2d
--------------------------------------------
 0101000000000000000000F03F000000000000F03F


test-# select force_collection(force_2d(asbinary('POINT(1 1)')));
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.


It seems that the crash is the result of the force_collection() function.
Perhaps these informations can help you to find out the problem.

I didn't understand what you mean with 
echo "SELECT asbinary('POINT(1 1)')" | valgrind --num-callers=10 postgres
and how to use it?

Best regards 

Horst

---------------------------------
 
Dr. Horst Düster 
GIS-Koordinator /Amtschef Stv.

Kanton Solothurn 
Amt für Geoinformation
Abteilung SO!GIS Koordination
Werkhofstr. 65
CH-4509 Solothurn 

Tel.: ++41 (0)32 627 25 32 
Fax: ++41 (0)32 627 22 14

horst.duester at bd.so.ch 
www.sogis.so.ch



-----Ursprüngliche Nachricht-----
Von: strk at refractions.net [mailto:strk at refractions.net]
Gesendet am: Donnerstag, 27. Januar 2005 14:44
An: Düster Horst
Cc: 'PostGIS Users Discussion'
Betreff: Re: [postgis-users] MapServer and PostGIS 1 RC1 and RC2

On Thu, Jan 27, 2005 at 02:11:58PM +0100, Düster Horst wrote:
> > What OS ? What postgresql version ?
> RedHat 7.2 i586
> Postgresql 8.0.0
> gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-124.7.2)
> 
> > Any warning at build time ?
> No warnings except of defined but unused variables during build of
postgis.
> 
> I dropped the whole postgresql/ postgis installation and DB-Clusetr
> inclusive all sources.
> Then I rebuild postgres with the following ./configure options: 
> 
> LDFLAGS=-lstdc++ ./configure \
>   --prefix=/usr/local/pgsql/current \
>   --enable-multibyte
> 
> OK. Postgresql was build and installed without any problems and works. 
> Next step build postgis with the use of GEOS and without GEOS.
> 
> In both cases postgresql crashes. I'm stumped!

What you can try is feeding the simplest crashing query 
to valgrind and send a report. For example:

echo "SELECT asbinary('POINT(1 1)')" | valgrind --num-callers=10 postgres

--strk;

> 
>  
> Dr. Horst Düster 
> GIS-Koordinator /Amtschef Stv.
> 
> Kanton Solothurn 
> Amt für Geoinformation
> Abteilung SO!GIS Koordination
> Werkhofstr. 65
> CH-4509 Solothurn 
> 
> Tel.: ++41 (0)32 627 25 32 
> Fax: ++41 (0)32 627 22 14
> 
> horst.duester at bd.so.ch 
> www.sogis.so.ch
> 
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: strk at refractions.net [mailto:strk at refractions.net]
> Gesendet am: Donnerstag, 27. Januar 2005 12:18
> An: Düster Horst
> Cc: 'postgis-users at postgis.refractions.net'
> Betreff: Re: [postgis-users] MapServer and PostGIS 1 RC1 and RC2
> 
> I don't get the same result:
>   
>   [lo:asbinary_crash]$ cat test.sql
>   select postgis_full_version();
>   create table test_pnt (id serial);
>   select
addgeometrycolumn('public','test_pnt','wkb_geometry',-1,'POINT',2);
>   insert into test_pnt (wkb_geometry) values
(Geometryfromtext('POINT(610000
> 230000)',-1));
>   SELECT asbinary(force_collection(force_2d(wkb_geometry)),'NDR') FROM
> test_pnt;
>   SELECT summary(wkb_geometry) from test_pnt;
>   
>   
>   [lo:asbinary_crash]$ psql -etf test.sql test
>   select postgis_full_version();
>    POSTGIS="1.0.0RC2" GEOS="2.1.1" PROJ="Rel. 4.4.8, 3 May 2004" USE_STATS
> DBPROC="0.1.0" RELPROC="0.1.0"
>   
>   create table test_pnt (id serial);
>   psql:test.sql:2: NOTICE:  CREATE TABLE will create implicit sequence
> "test_pnt_id_seq" for serial column "test_pnt.id"
>   CREATE TABLE
>   select
addgeometrycolumn('public','test_pnt','wkb_geometry',-1,'POINT',2);
>    public.test_pnt.wkb_geometry SRID:-1 TYPE:POINT DIMS:2
>    geometry_column fixed:0
>   
>   insert into test_pnt (wkb_geometry) values
(Geometryfromtext('POINT(610000
> 230000)',-1));
>   INSERT 11512442 1
>   SELECT asbinary(force_collection(force_2d(wkb_geometry)),'NDR') FROM
> test_pnt;
>  
>
\001\007\000\000\000\001\000\000\000\001\001\000\000\000\000\000\000\000\240
> \235"A\000\000\000\000\200\023\014A
>   
>   SELECT summary(wkb_geometry) from test_pnt;
>   
>   Point[]
> 
> What OS ? What postgresql version ?
> Any warning at build time ?
> 
> --strk;
> 
> On Thu, Jan 27, 2005 at 12:02:18PM +0100, Düster Horst wrote:
> > > You mean 'geometry', right ?
> > 
> > Of course I meant type of geometry.
> > 
> > 
> > > Also, did you dump/reload or manually upgrade postgis ?
> > I created a new blank PostgreSQL-8.0.0 DB with:
> > # createdb test
> > # createlang plpgsql test
> > # psql -d test -f lwpostgis.sql
> > 
> > 
> > > Can you reproduce the bug on a single POINT geometry ?
> > Here the steps that produces a single POINT geometry and leads to the
> server
> > crash:
> > 
> > # create table test_pnt (id serial);
> > CREATE TABLE
> > 
> > # select
> addgeometrycolumn('public','test_pnt','wkb_geometry',-1,'POINT',2);
> >                                 addgeometrycolumn
> >
>
----------------------------------------------------------------------------
> > -----
> >  public.test_pnt.wkb_geometry SRID:-1 TYPE:POINT DIMS:2
> >  geometry_column fixed:0
> > (1 row)
> > 
> > # insert into test_pnt (wkb_geometry) values
> (Geometryfromtext('POINT(610000
> > 230000)',-1));
> > INSERT 16691569 1
> > 
> > # SELECT asbinary(force_collection(force_2d(wkb_geometry)),'NDR') FROM
> > test_pnt;
> > server closed the connection unexpectedly
> >       This probably means the server terminated abnormally
> >       before or while processing the request.
> > 
> > 
> > > If you can show me summary(that_point)
> > 
> > # select summary(wkb_geometry) from test_pnt;
> >   summary
> > -----------
> > 
> > Point[]
> > 
> > (1 row)
> > 
> > 
> >  
> > Dr. Horst Düster 
> > GIS-Koordinator /Amtschef Stv.
> > 
> > Kanton Solothurn 
> > Amt für Geoinformation
> > Abteilung SO!GIS Koordination
> > Werkhofstr. 65
> > CH-4509 Solothurn 
> > 
> > Tel.: ++41 (0)32 627 25 32 
> > Fax: ++41 (0)32 627 22 14
> > 
> > horst.duester at bd.so.ch 
> > www.sogis.so.ch
> > 
> > 
> > 
> > -----Ursprüngliche Nachricht-----
> > Von: strk at refractions.net [mailto:strk at refractions.net]
> > Gesendet am: Donnerstag, 27. Januar 2005 09:44
> > An: Düster Horst
> > Cc: 'postgis-users at postgis.refractions.net'
> > Betreff: Re: [postgis-users] MapServer and PostGIS 1 RC1 and RC2
> > 
> > On Thu, Jan 27, 2005 at 09:39:03AM +0100, Düster Horst wrote:
> > > strk
> > > 
> > > > What type is  wkb_geometry ?
> > > 
> > > wkb_geometry is type of POINT
> > 
> > You mean 'geometry', right ?
> > 
> > > 
> > > > Did you try manually issuing the query ? 
> > > >   # SELECT asbinary(force_collection(force_2d(wkb_geometry)),'NDR')
> > > >    FROM avt_asit_unfall;
> > > 
> > > PostgreSQL responsed with
> > > 
> > > server closed the connection unexpectedly
> > > 	This probably means the server terminated abnormally
> > > 	before or while processing the request.
> > 
> > Can you reproduce the bug on a single POINT geometry ?
> > If you can show me summary(that_point).
> > Also, did you dump/reload or manually upgrade postgis ?
> > 
> > --strk;
> > 
> > > 
> > > 
> > > Dr. Horst Düster 
> > > GIS-Koordinator /Amtschef Stv.
> > > 
> > > Kanton Solothurn 
> > > Amt für Geoinformation
> > > Abteilung SO!GIS Koordination
> > > Werkhofstr. 65
> > > CH-4509 Solothurn 
> > > 
> > > Tel.: ++41 (0)32 627 25 32 
> > > Fax: ++41 (0)32 627 22 14
> > > 
> > > horst.duester at bd.so.ch 
> > > www.sogis.so.ch
> > > 
> > > 
> > > 
> > > -----Ursprüngliche Nachricht-----
> > > Von: strk at refractions.net [mailto:strk at refractions.net]
> > > Gesendet am: Donnerstag, 27. Januar 2005 09:29
> > > An: Düster Horst
> > > Cc: 'postgis-users at postgis.refractions.net'
> > > Betreff: Re: [postgis-users] MapServer and PostGIS 1 RC1 and RC2
> > > 
> > > On Thu, Jan 27, 2005 at 09:03:18AM +0100, Düster Horst wrote:
> > > > Now my third attempt to get an answer of my posted question.
> > > > Since a time I'm playing with MapServer 4.4.1 and PostGIS 1RC1 and
RC2
> > > since
> > > > today with semi
> > > > success. I'm able to create maps with polygon and line layers from
> > > PostGIS,
> > > > but PostGIS/Postgres crashes with the error message (see below) when
I
> > > > use a point layer. This crash appears exclusively with all my point
> > layers
> > > > which work fine with MS 4.4.1 and Postgis 0.8. Do there exist any
> > > > restrictions of using PostGIS 1 with MapServer 4.4.1?? 
> > > > 
> > > > I would be appreciate about any hint.
> > > > 
> > > > With best regards
> > > > 
> > > > Horst
> > > > 
> > > > Mapfile snippet:
> > > > 
> > > > ...
> > > > LAYER
> > > >   CONNECTIONTYPE POSTGIS
> > > >   CONNECTION 'dbname=xx host=xx user=xx port=5432'
> > > >   DATA "wkb_geometry from asit2 USING UNIQUE ogc_fid USING SRID=-1"
> > > >   TYPE POINT
> > > > ...
> > > 
> > > What type is  wkb_geometry ?
> > > 
> > > Did you try manually issuing the query ? 
> > >   # SELECT asbinary(force_collection(force_2d(wkb_geometry)),'NDR')
> > >     FROM avt_asit_unfall;
> > > 
> > > --strk;
> > > 
> > > > 
> > > > 
> > > > 
> > > > Error message:
> > > > > msDrawMap(): Image handling error. Failed to draw layer named
> 'asit2'.
> > 
> > > > > msPOSTGISLayerWhichShapes(): Query error. Error executing POSTGIS
> SQL
> > > > > statement (in FETCH ALL): DECLARE mycursor BINARY CURSOR FOR
SELECT
> > > > >
> > > >
> > >
> >
>
ANZ_TOT::text,asbinary(force_collection(force_2d(wkb_geometry)),'NDR'),ogc_f
> > > > > id::text from avt_asit_unfall WHERE wkb_geometry &&
> > > > setSRID('BOX3D(588837.5
> > > > > 213700,648462.5 261400)'::BOX3D, -1 ) -server closed the
connection
> > > > > unexpectedly This probably means the server terminated abnormally
> > before
> > > > or
> > > > > while processing the request. Error with POSTGIS data variable.
You
> > > > > specified ''.
> > > > > Standard ways of specifiying are : 
> > > > > (1) 'geometry_column from geometry_table' 
> > > > > (2) 'geometry_column from (<sub query>) as foo using unique
<column
> > > name>
> > > > > using SRID=<srid#>' 
> > > > >
> > > > > Make sure you put in the 'using unique <column name>' and 'using
> > SRID=#'
> > > > > clauses in. 
> > > > >
> > > > > For more help, please see
> > > http://postgis.refractions.net/documentation.php
> > > > 
> > > > >
> > > > > Mappostgis.c - version of Jan 23/2004. 
> > > > 
> > > > 
> > > > 
> > > > ---------------------------------
> > > >  
> > > > Dr. Horst Düster 
> > > > GIS-Koordinator /Amtschef Stv.
> > > > 
> > > > Kanton Solothurn 
> > > > Amt für Geoinformation
> > > > Abteilung SO!GIS Koordination
> > > > Werkhofstr. 65
> > > > CH-4509 Solothurn 
> > > > 
> > > > Tel.: ++41 (0)32 627 25 32 
> > > > Fax: ++41 (0)32 627 22 14
> > > > 
> > > > horst.duester at bd.so.ch 
> > > > www.sogis.so.ch
> > > > 
> > > > _______________________________________________
> > > > postgis-users mailing list
> > > > postgis-users at postgis.refractions.net
> > > > http://postgis.refractions.net/mailman/listinfo/postgis-users
> > > _______________________________________________
> > > postgis-users mailing list
> > > postgis-users at postgis.refractions.net
> > > http://postgis.refractions.net/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users



More information about the postgis-users mailing list