I had a large table of zip & postal codes which always crashed after
about 20 minutes of geocoding them in the ipython shell, i did the
same thing several times on the same os, but on a 32-bit machine with
no issues. running under mod-python or mod-wsgi on the 64-bit box
also seems to randomly th
> "The same problem [segfault] could afflict any python package that
> uses Ctypes on 64-bit systems without explicitly marking argument and
> return types. "
>
> Looking back through the modwsgi thread and this one, everyone's on
> 64bit, except the CentOS guy who said it worked ok on 32bit but n
Hi,
On Dec 3, 5:21 pm, Andre P LeBlanc <[EMAIL PROTECTED]> wrote:
> Confirmed also. only happens on my 64-bit machine, and is not related
> to apache at all as I can reproduce it faithfully in ipython.
>
I tried pretty hard to replicate it in the console and couldn't - none
of our unit tests cra
Confirmed also. only happens on my 64-bit machine, and is not related
to apache at all as I can reproduce it faithfully in ipython.
On Dec 2, 8:32 pm, GRoby <[EMAIL PROTECTED]> wrote:
> I can confirm that all of my seg faults were all on my 64 bit machine
> but could not be duplicated when I trie
I can confirm that all of my seg faults were all on my 64 bit machine
but could not be duplicated when I tried to on my 32 bit test virtual
machines.
On Dec 2, 7:40 pm, rcoup <[EMAIL PROTECTED]> wrote:
> Posting to geos-devel, I got this reply from Paul
> Ramsey:http://lists.osgeo.org/pipermail
On Dec 3, 1:40 pm, rcoup <[EMAIL PROTECTED]> wrote:
> Leading me to:http://sgillies.net/blog/829/shapely-1-0-8/
>
> "The same problem [segfault] could afflict any python package that
> uses Ctypes on 64-bit systems without explicitly marking argument and
> return types. "
The relevant changeset i
Posting to geos-devel, I got this reply from Paul Ramsey:
http://lists.osgeo.org/pipermail/geos-devel/2008-December/003800.html
Leading me to: http://sgillies.net/blog/829/shapely-1-0-8/
"The same problem [segfault] could afflict any python package that
uses Ctypes on 64-bit systems without expl
On Nov 26, 6:07 am, Justin Bronn <[EMAIL PROTECTED]> wrote:
> I created an Ubuntu 8.10 VM to try and test out this problem.
> However, the only way that I could reproduce your exact problem
> (segfault upon HTTP request) is when using the mpm-worker (threaded)
> Apache. When using the prefork,
FWIW --
I got this working in CentOS5.2 by removing the default (yum installed)
version of apache, and compiling the latest version, 2.2.10.
While I was at it, I compiled the latest version of mod_python.
That was all it took, and now, no more segmentation violations.
Thanks,
Liam
Justin Bronn
> I reran my tests with the latest version of Apache on my 8.10 test
> machine. I am no longer getting the Segfaults with either worker or
> prefork. I am now getting an Invalid SRS type "wkt" error (that I
> assume you are now running into).
Yup that's the error I got: http://code.djangoprojec
Justin,
I reran my tests with the latest version of Apache on my 8.10 test
machine. I am no longer getting the Segfaults with either worker or
prefork. I am now getting an Invalid SRS type "wkt" error (that I
assume you are now running into).
I have tried several things (including downgrading
> Based on comments in a separate thread, GeoDango may have issues with
> multithreaded configuration. Which Apache MPM was being used for each
> Apache version, prefork or worker? The worker MPM uses threads and so
> that could be the culprit.
Yes -- the libraries GeoDjango uses, GEOS and GDAL,
I reported a similar problem in October. Since then, I have tested on a
new server and am experiencing the same problem. This one is on an
CentOS 5.2 EC2 machine configured as below... I wonder if noting the
workaround discovered by GRoby will give the developers any clues as to
what is going on.
Both of them are using the mpm-worker package. I tested the 2.2.9
version with mpm-prefork and mpm-event, they all gave the same
Segmentation Fault errors (rebooting the server in between installing
each).
Greg
On Nov 18, 6:53 pm, Graham Dumpleton <[EMAIL PROTECTED]>
wrote:
> Based on comments
Based on comments in a separate thread, GeoDango may have issues with
multithreaded configuration. Which Apache MPM was being used for each
Apache version, prefork or worker? The worker MPM uses threads and so
that could be the culprit.
Graham
On Nov 19, 10:43 am, GRoby <[EMAIL PROTECTED]> wrote
I replaced packages one at a time with ones from Ubuntu 8.04. The
segmentation faults went away when I switched Apache from 2.2.9 to
2.2.8, so I can just lock the package with the Hardy version for now.
On Nov 18, 4:34 pm, GRoby <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I created a GeoDjango appl
Hello,
I created a GeoDjango application that I have been successfully using
with Ubuntu 8.04.
I would like to have as many packages as possible handled by the OS,
so I am testing it with Ubuntu 8.10, with all packages installed
through Synaptic (including PostGIS, PostGreSQL, Mod-Python, Psycop
17 matches
Mail list logo
