Read: http://code.google.com/p/modwsgi/wiki/ConfigurationIssues
But as explained by someone else, you need to override where UNIX sockets for daemon listener are placed. Usually under Ubuntu the default is fine and is only RedHat derived systems which is an issue and need to be changed. Graham On 3 February 2010 08:10, wildabeast <[email protected]> wrote: > When I start up apache: > > [Tue Feb 02 20:31:12 2010] [alert] (2)No such file or directory: > mod_wsgi (pid=10924): Couldn't bind unix domain socket '/etc/apache2/ > run/wsgi.10924.0.1.sock'. > > And when I make a request which should go to my wsgi app: > > [Tue Feb 02 20:31:20 2010] [error] [client XX.XX.XX.XX] (2)No such > file or directory: mod_wsgi (pid=10931): Unable to connect to WSGI > daemon process 'bespin' on '/etc/apache2/run/wsgi.10924.0.1.sock' > after multiple attempts., referer: http://XX.XX.XX.XX/ > > I have a feeling I am missing a configuration step or something, but > I'm not sure what. > > I have /etc/apache2/mods-available : > LoadModule wsgi_module /usr/lib/apache2/modules/mod_wsgi.so > > and /usr/lib/apache2/modules/mod_wsgi.so exists. > > Help would be appreciated! > > -- > 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. > > -- 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.
