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. I guess I'll move to Apache 2.2.8 and see if that helps. Again, it works fine from the command line, but only seg viols when using Apache. Justin was good enough to run a test case I created and was unable to duplicate the error. I'm wondering now about the exact versions of Apache and other components that might be causing the problem.
> Linux domU-12-31-39-02-94-32 2.6.16.33-xenU #2 SMP Wed Aug 15 17:27:36 > SAST 2007 x86_64 x86_64 x86_64 GNU/Linux > mod_python.x86_64 3.2.8-3.1 installed > python.x86_64 2.4.3-19.el5 > installed The Apache configuration: > Server version: Apache/2.2.3 > Server built: Nov 10 2007 12:44:14 > Server's Module Magic Number: 20051105:3 > Server loaded: APR 1.2.7, APR-Util 1.2.7 > Compiled using: APR 1.2.7, APR-Util 1.2.7 > Architecture: 64-bit > Server MPM: Prefork > threaded: no > forked: yes (variable process count) > Server compiled with.... > -D APACHE_MPM_DIR="server/mpm/prefork" > -D APR_HAS_SENDFILE > -D APR_HAS_MMAP > -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) > -D APR_USE_SYSVSEM_SERIALIZE > -D APR_USE_PTHREAD_SERIALIZE > -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT > -D APR_HAS_OTHER_CHILD > -D AP_HAVE_RELIABLE_PIPED_LOGS > -D DYNAMIC_MODULE_LIMIT=128 > -D HTTPD_ROOT="/etc/httpd" > -D SUEXEC_BIN="/usr/sbin/suexec" > -D DEFAULT_PIDLOG="logs/httpd.pid" > -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" > -D DEFAULT_LOCKFILE="logs/accept.lock" > -D DEFAULT_ERRORLOG="logs/error_log" > -D AP_TYPES_CONFIG_FILE="conf/mime.types" > -D SERVER_CONFIG_FILE="conf/httpd.conf" GRoby 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 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, Psycopg2, >> Django, etc). >> >> In a Python Shell, I am able to perform queries on my spatial models >> successfully. In a web browser, I get a plain white screen if any >> code is executed that works with spatially enabled models. Otherwise >> everything seems to be working (including an OpenLayers MapServer >> view, so I know the DB is loaded correctly). >> >> In the error.log file, I get a single error per attempted page view >> like: >> [Tue Nov 18 16:13:43 2008] [notice] child pid 21074 exit signal >> Segmentation fault (11) >> [Tue Nov 18 16:16:59 2008] [notice] child pid 21071 exit signal >> Segmentation fault (11) >> [Tue Nov 18 16:19:08 2008] [notice] child pid 21328 exit signal >> Segmentation fault (11) >> >> If I attempt to run the same code in a Python Shell, the code runs >> correctly. >> >> Any ideas, I suspect that it could be a permission or Mod-Python >> related issue but am not sure where to go from here. >> >> Thanks! >> >> BTW, if anyone wants a copy of the application, it is available >> fromhttp://www.coopgis.org, it is the start of an Electric Utility GIS. >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
