The “can’t start new thread” error almost certainly due to the fact that you have already have too many threads running within your python process, and due to a resource limit of some kind the request to create a new thread is refused. You should probably look at the number of threads you’re creating; the … Read more
That error, without any sort of Python traceback, may be a variation on issue described in: http://code.google.com/p/modwsgi/issues/detail?id=29&can=1 That is, occurs when HTTP client connection is lost before the full response could be written back by the web server. It can manifest as ‘client closed connection’, ‘failed to write data’ or ‘failed to flush data’ IOError … Read more
I’ve had multiple WSGI apps running on a single Apache install, and found that the easiest thing to do is just have multiple process groups– one for each of the apps. One downside, versus actually trying to get a single process to run both (or more) apps, is that this might use a little more … Read more
sudo apt-get install libapache2-mod-wsgi-py3 This will replace libapache2-mod-wsgi and will restart the apache service. More specific instructions (Django) are available for here: https://docs.djangoproject.com/en/1.8/howto/deployment/wsgi/modwsgi/
Should I use one web server or two? The context of this question is that lots of people recommend using NginX to serve static media files and Apache to serve the Python, which beckons the following questions: Why can’t we use just one server. I understand Apache may be a beast at times, therefore I … Read more
mod_python is dead, so using mod_python probably isn’t a good idea for new projects. Personally, I prefer to use mod_wsgi over CGI (or FastCGI). It’s dead-simple to set up, and much more efficient.
I think you should change: Alias /media/ “/usr/lib/python2.6/site-packages/django/contrib/admin/media” to: Alias /static/admin/ “/usr/lib/python2.6/site-packages/django/contrib/admin/media” Because you have: ADMIN_MEDIA_PREFIX = ‘/static/admin/’
Try to enable wsgi mod in Apache sudo a2enmod wsgi If you come across below error ERROR: Module mod-wsgi does not exist! You will have to install mod wsgi as below. What you have to do is run the following commands, sudo apt-get install libapache2-mod-wsgi sudo a2enmod wsgi sudo service apache2 restart
Django 1.6 has added persistent connections support (link to doc for latest stable Django ): Persistent connections avoid the overhead of re-establishing a connection to the database in each request. They’re controlled by the CONN_MAX_AGE parameter which defines the maximum lifetime of a connection. It can be set independently for each database.