Which means that you must have multiple WSGIDaemonProcess directives
for same name in your Apache configuration file. That or if using
include to include your snippet, you are including it twice somehow.
Either way, a WSGIDaemonProcess for same name is being seen twice.
> My vhost config for my domain is as follows:
>
> <VirtualHost *:80>
>
> ServerName www.example.com
>
> WSGIDaemonProcess www.example.com user=www-data group=www-data
> threads=10
There is no point setting user/group here as those are the user/group
that Apache runs as anyway. You only need to set them if you want to
use something different.
> WSGIProcessGroup www.example.com
>
> Alias /static/ /var/www/www.example.com/static/
>
> <Directory /var/www/www.example.com/static>
> Order allow,deny
> Allow from all
> </Directory>
>
> WSGIScriptAlias / /home/jonathan/src/website/apache/django.wsgi
>
> <Directory /home/jonathan/src/website/apache>
> Order allow,deny
> Allow from all
> </Directory>
>
> LogLevel warn
> ErrorLog /var/log/apache2/example.com/error.log
> CustomLog /var/log/apache2/example.com/access.log combined
>
> </VirtualHost>
>
> I have other vhosts, however none are using mod_wsgi - they are just
> serving basic PHP sites.
>
> Grepping the output of ps aux for wsgi doesn't show any wsgi processes
> running.
That is because they will show as httpd process unless you use
'display-name' option to WSGIDaemonProcess. See:
http://code.google.com/p/modwsgi/wiki/ConfigurationDirectives#WSGIDaemonProcess
> I noticed someone with a similar error posting another discussion in
> the group, but still I have not been able to resolve this issue.
>
> Any ideas what I am doing wrong?
Also ensure you are using most up to date mod_wsgi and not some older version.
Graham