I'm using pre-fork mode. Apache version is 2.0.63. this is on RedHat so i'm not sure that the comments about SELinux apply?
I tried turning off mod_php and still have the same problem. So it looks like the conflict is between mod_wsgi and another apache module or the apache binary? Is it possible to run mod_wsgi in daemon mode in prefork mode? I'm getting the impression not. So - would my best bet be to re-compile Apache for worker mode? thanks Justin On Oct 10, 10:28 pm, Graham Dumpleton <[email protected]> wrote: > Temporarily disable php module in apache to verify whether is mod_wsgi > or conflict with php. Also ensure selinux disabled if on Linux. > > I'll be in position to start answering emails properly in another > couple of days. > > > > On Sunday, October 10, 2010, Kropotkin <[email protected]> wrote: > > Thanks all > > > I set up for daemon mode in a virtual host. I get 2 httpd processes > > started for this. All looks pretty stable. But I still get the httpd > > <defunct> processes and the Segmentation fault for my 20 processes (my > > usual number of spawned processes). And the test app for wsgi doesn't > > work. In fact the server is unreachable. Now I'm getting this even > > with mod_php removed. So it looks like a conflict between mod_wsgi and > > Apache. I've checked it does appear to be the correct version of apxs > > I've compiled against. > > > Hmm. Not looking very encouraging at this point. > > > ~Justin > > > On Oct 8, 11:40 pm, Carl Nobile <[email protected]> wrote: > >> In general mod_wsgi will not work well with mod_php or mod_python, try > >> configuring your mod_wsgi apps to use daemon mode this may bring > >> better luck. > > >> ~Carl > > >> On Fri, Oct 8, 2010 at 6:01 PM, Kropotkin <[email protected]> > >> wrote: > >> > Just trying to install mod_wsgi 3.3. on my system > >> > Apache 2.0.52 in prefork mode on RedHat Linux with PHP 5.2.13 > > >> > My httpd processes start, they appear to take up no memory, have > >> > 'defunct' next to them and then go away. In the logs I find lines like > >> > this: child pid 12103 exit signal Segmentation fault (11). I think > >> > this is not when mod_wsgi is being loaded but on the first request. > > >> > The conflict is with mod_php. When I remove that all is fine. I tried > >> > removing all my PHP extensions but that did not fix it. > > >> > I did have python 2.3.4 installed and mod_wsgi would not compile > >> > against that but I installed 2.6 and ran configure with this ./ > >> > configure --with-python=/path/to/my/python2.6] and compile seemed to > >> > be fine - I got the so. > > >> > Not sure where to go next > > >> > Thanks for any steers > > >> > Justin Wyllie > > >> > -- > >> > 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 > >> > athttp://groups.google.com/group/modwsgi?hl=en. > > >> -- > >> --------------------------------------------------------------------------- > >> ---- > >> Carl J. Nobile (Software Engineer) > >> [email protected] > >> --------------------------------------------------------------------------- > >> ---- > > > -- > > 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 > > athttp://groups.google.com/group/modwsgi?hl=en. -- 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.
