Re: problem with threaded apache
Yes, I've disabled it now, and all is good! --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
Do you have SELinux enabled? Check /var/log/audit/audit.log and/or try disabling it by editing /etc/sysconfig/selinux and rebooting. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
> I started to rev back mod_python and ran into a few dependency problems. I'll > keep trying and see if that helps. Will let you know... The REAL problem between my working (openhosting.com virtual) Fedora system and this one was SELinux. Aarrgghh! And of course I didn't have any problems in single user mode! Thank you Yango for your comment on http://www.djangoproject.com/documentation/modpython/ That's what I get for not using Red Hat for a few years... DDOS: Dumbass Denial of Service -rob --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
Thanks for the replies everybody. This is good info and I need to know more about apache in general. Unfortunately it doesn't solve the problem! I am using the vanilla Fedora rpm for httpd which builds in prefork.c and has generally default module directives. The funny behaviour is that it runs fine in -X mode but doesn't run well with multiple forks. My mistake for naming it multithreading, and sorry for not being clearer about that. One difference I've found with my new server is that I am running mod_python 3.2.8. On my old server I ran 3.1.4. I've also seen other posts with people having similar problems, particularly on http://www.djangoproject.com/documentation/modpython/ I started to rev back mod_python and ran into a few dependency problems. I'll keep trying and see if that helps. Will let you know... -rob --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
On 4/21/06, Richie Hindle <[EMAIL PROTECTED]> wrote: > For what it's worth, I think this advice should be in the documentation. > The documentation says "Apache with mod_python currently is the preferred > setup for using Django on a production server" but it doesn't explain > which MPM. Good call. I've updated the docs. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
I've been running django (trunk and M-R) on apache prefork with no problems. I recently switched to the worker MPM, and so far, everything seems to work fine (with better memory usage, I might add). I did have a problem on a separate installation, however, related to memcache. I think there may be a deadlock problem when using memcache and the worker MPM, but I haven't investigated it much yet. But I can confirm that this combination works for me:FreeBSD 6.0Apache 2.0.55 with worker mpmpython 2.4.3mod_python 3.2.8psycopg 1.1.21postgresql 8.1.3 On 4/21/06, Richie Hindle <[EMAIL PROTECTED]> wrote: [Jacob]> I'd suggest switching to the "prefork" MPM for ApacheFor what it's worth, I think this advice should be in the documentation.The documentation says "Apache with mod_python currently is the preferred setup for using Django on a production server" but it doesn't explainwhich MPM.--Richie Hindle[EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
[Jacob] > I'd suggest switching to the "prefork" MPM for Apache For what it's worth, I think this advice should be in the documentation. The documentation says "Apache with mod_python currently is the preferred setup for using Django on a production server" but it doesn't explain which MPM. -- Richie Hindle [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: problem with threaded apache
On Apr 21, 2006, at 12:06 AM, oggie rob wrote: > Any ideas what I am facing here? Or how to debug this? I'd suggest switching to the "prefork" MPM for Apache; I've always seen better performance and stability running Django under it as opposed to the threaded one. Don't know if that's you're specific issue, but everything else looks identical to our (working) deployment architecture at work, so... Jacob --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
