Arrgh, not that issue. Ie., __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALI TY___YOU_MUST_EXEC__()
I have seen this before and we got no where in working it out except that some special MacOS X framework and/or function was being used that had some restrictions on it. If you create a separate discussion on mod_wsgi list, will at least sit there to remind me and can do some more research on it again. Graham On Oct 4, 8:29 am, Jashugan <[EMAIL PROTECTED]> wrote: > On Sep 24, 5:05 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > > > To really get to the problem, you may need to start up Apache in > > > > single process mode and run it in a debugger. For details see: > > > > >http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Debugging_C... > > So I tried mod_wsgi, but ran into the same problems as with > mod_python. Namely: > > The process has forked and you cannot use this CoreFoundation > functionality safely. You MUST exec(). > Break on > __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALI > TY___YOU_MUST_EXEC__() > to debug. > ... snip 50 lines of the same error above repeating itself ... > [Fri Oct 03 14:58:16 2008] [error] [client 10.10.6.1] Premature end of > script headers: conf.wsgi > [Fri Oct 03 14:58:17 2008] [notice] child pid 25258 exit signal Trace/ > BPT trap (5) > > Here is the configuration I used: > > WSGIDaemonProcess site-1 user=www group=www processes=5 threads=1 > WSGIProcessGroup site-1 > > WSGIScriptAlias /ri /opt/local/var/www/django/ri/lib/apache/conf.wsgi > > <Directory /opt/local/var/www/django/ri/lib/apache> > Order deny,allow > Allow from all > </Directory> > > Here is the output of httpd -V: > > Server version: Apache/2.2.8 (Unix) > Server built: Apr 22 2008 14:47:50 > Server's Module Magic Number: 20051115:11 > Server loaded: APR 1.3.2, APR-Util 1.3.2 > Compiled using: APR 1.2.12, APR-Util 1.2.12 > Architecture: 32-bit > Server MPM: Prefork > threaded: no > forked: yes (variable process count) > Server compiled with.... > -D APACHE_MPM_DIR="server/mpm/prefork" > -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="/opt/local/apache2" > -D SUEXEC_BIN="/opt/local/apache2/bin/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" > > The solution we are using right now is a custom HTTP job server that > will receive function requests and process them. However, I would > rather get the solution working in Apache if possible in order to keep > things simple. > > Also, Graham, do you want me to create a new thread in the mod_wsgi > google mailing list? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
