First off, upgrade to mod_python 3.3.1 and stop using the older version of mod_python. This will eliminate it being a problem with the older version of mod_python that has been fixed. There were an awful lot of fixes and improvements made in mod_python 3.3.1.
Second, as a quick check, make sure you aren't hitting the most common reason for crashes when using mod_python by checking out: http://www.dscpl.com.au/wiki/ModPython/Articles/ExpatCausingApacheCrash Finally, try and work out where it is crashing by doing the following: apachectl stop gdb /some/path/httpd In gdb do: run -DONE_PROCESS Then use the Trac application via your web browser until it crashes. In gdb then do: where Analyse the stack trace to identify where it crashes and if you can't make sense of it, post the stack trace here. If people here think its all a bit off topic, get onto the mod_python users mailing list and post all the details including stack trace there. Graham On Apr 15, 6:21 am, "Ralf G. R. Bergs" <[EMAIL PROTECTED]> wrote: > Hi there, > > I'm running Debian stable's version of Trac (0.10.3-1) under Apache > 2.2.3-4 with Python 2.4.4-2 andmod_python3.2.10-4. > > Before I switched to usingmod_pythontoday, Trac was working > perfectly. Now I can't create tickets anymore. The preview functions > works just fine, but as soon as I press "Submit ticket" I only receive > an empty page. Firefox' "Live HTTP Headers" extension shows me that > all I receive is the "200 OK," not a single response header, and no > HTTP body either. > > I noticed several things, tho, that are pretty concrete and might > point you to the cause of my problem. First, my ability to create > tickets returns as soon as I disable SMTP notifications (by setting > "smtp_enabled = false"). Second, the Apache child seems to crash > because I find the following in Apache's error log: > > [notice] child pid 1204 exit signal Segmentation fault (11) > > The Trac logfile doesn't show anything (meaningful), altho I'm running > on DEBUG level. > > And, of course, disablingmod_pythonalso brings back my ability to > create tickets. But I would like to continuemod_pythonfor speed > reasons. > > Here's some snippets from out of my Apache config file (note that this > is an SSL-enabled server): > > Alias /trac "/usr/share/trac/htdocs/" > <Directory "/usr/share/trac/htdocs/"> > Options Indexes MultiViews > AllowOverride None > Order allow,deny > Allow from all > </Directory> > > <Location "/cgi-bin/trac.cgi"> > SetEnv PYTHON_EGG_CACHE "/var/cache/trac/egg_cache" > SetEnv HTTPS 1 > # Only whenmod_pythonNOT in use > #SetEnv TRAC_ENV "/var/lib/trac" > # Python-specific options > SetHandlermod_python > PythonInterpreter main_interpreter > PythonDebug on > PythonOption TracEnv /var/lib/trac > PythonOption TracUriRoot /cgi-bin/trac.cgi > PythonHandler trac.web.modpython_frontend > </Location> > > I use the additional macros/plugins Debbug, TracTags-0.4-py2.4.egg, > TracTocMacro-1.0-py2.4.egg. > > My guess would be from my above observations that for some unknown > reason, Trac when run inmod_pythoncan't send the notification e-mail > message when creating the ticket, and thus the child dies (or it can't > send because the child dies earlier.) > > Would you agree to this interpretation? What could be the reason? How > can I get Trac running properly withmod_python? > > Thanks, > > Ralf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
