[MAPSERVER-USERS] CLOSE_CONNECTION=DEFER - Segmentation fault
Ivan Mincik
ivan.mincik at gmail.com
Wed Mar 5 04:26:36 PST 2008
Nothing is perfect. There are no problems with applied patch when browsing the
map. But when I use identify object query from php5-mapscript the problem is
rising again.
I have in postgresql log:
2008-03-05 13:19:30 CET WARNING: there is no transaction in progress
2008-03-05 13:19:30 CET ERROR: cursor "mycursor" does not exist
2008-03-05 13:19:31 CET ERROR: DECLARE CURSOR may only be used in transaction
blocks
2008-03-05 13:19:31 CET WARNING: there is no transaction in progress
2008-03-05 13:19:31 CET ERROR: cursor "mycursor" does not exist
2008-03-05 13:19:32 CET ERROR: DECLARE CURSOR may only be used in transaction
blocks
2008-03-05 13:19:32 CET WARNING: there is no transaction in progress
2008-03-05 13:19:32 CET ERROR: cursor "mycursor" does not exist
2008-03-05 13:19:34 CET ERROR: DECLARE CURSOR may only be used in transaction
blocks
2008-03-05 13:19:34 CET WARNING: there is no transaction in progress
2008-03-05 13:19:34 CET ERROR: cursor "mycursor" does not exist
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: autovacuum: processing database "gisplan"
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:10 CET LOG: could not receive data from client: Connection
reset by peer
2008-03-05 13:20:10 CET LOG: unexpected EOF on client connection
2008-03-05 13:20:40 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:40 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:41 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:42 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:43 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:43 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:44 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:44 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:45 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:45 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:45 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:46 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:46 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:46 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:47 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:47 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:48 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:49 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:50 CET WARNING: there is already a transaction in progress
2008-03-05 13:20:50 CET WARNING: there is already a transaction in progress
ivan
On Monday 03 March 2008 21:53, rich.fromm wrote:
> hrach wrote:
> > I use mapserver 4.10.3, postgresql 8.1, Debian Etch.
> >
> > Is anybody using CLOSE_CONNECTION=DEFER without any problems ?
>
> I am now using it fine with mapserver 5.0.0 after applying the patch for
> bug 2497:
> http://trac.osgeo.org/mapserver/ticket/2497
>
> I don't know if 4.10.3 is different enough for that patch to be applicable
> or not. But if it's not too hard to upgrade, you might want to try a later
> version (e.g. 5.0.2) plus that patch. Note that the patch may make it into
> the 5.0.3 release (it was originally targetted for 5.2).
>
> You also might want to take a look at the following related mailing list
> threads:
>
> http://www.nabble.com/Segmentation-fault---mapserver---postgis-to12653945.h
>tml#a12674499
> http://www.nabble.com/postgres-transaction-warnings-to15749333.html
>
> - Rich
More information about the MapServer-users
mailing list