On 4 December 2011 13:51, Drew Yeaton <[email protected]> wrote: > On Dec 3, 2011, at 8:44 PM, Graham Dumpleton wrote: > >> On 3 December 2011 05:50, Drew Yeaton <[email protected]> wrote: >>> Answers inline, though I'm not sure how helpful this will be— >>> >>> On Dec 1, 2011, at 8:04 PM, Graham Dumpleton wrote: >>> >>>> What Apache and Python versions? >>> >>> Apache 2.2.8 >>> Python 2.5.2 >> >> I haven't compiled with Python 2.5 for a very log time. It is possible >> that changes to threading to make it compliant with Python 3.2 could >> have broken things for 2.5. > > What's the oldest Python you're planning to support?
It has always worked back to Python 2.3. Didn't have the intention of breaking it for older versions. I will have to go try and build it for some older versions to make sure okay. >>>> Definitely not still loading mod_python into same Apache? >>> >>> I don't believe so, but I don't know how to tell for sure. >>> >>>> Is it the whole of Apache that is crashing, or just mod_wsgi daemon >>>> process? >>> >>> Again, not sure how to tell. >> >> Does the seg fault occur just once when Apache is started and Apache >> then doesn't seem to be running at all, or do you get a never ending >> loop of seg faults in log, or does seg fault only happen on first >> request made to a Python WSGI application? > > Appears to happen just once. I attempted to start it multiple times, and got > a single fault in the log for each attempt. Find the actual Apache executable. Would be 'httpd' or 'apache'. Try running: httpd -X If that crashes then means the whole Apache parent process is crashing on startup. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en.
