Changing that configuration directive fixed it. Thanks Giel!
On Feb 2, 2:31 pm, Giel van Schijndel <[email protected]> wrote: > On Tue, Feb 02, 2010 at 02:22:44PM -0800, wildabeast wrote: > > On Feb 2, 1:10 pm, 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! > > > Some more info: > > - running Ubuntu 9.1 and Apache 2.2.12 > > - the folder /etc/apache2/run does not exist ... should it? > > I'm using Debian Lenny on one of my systems with 2.2.12 as well. Most > packages in Ubuntu tend to be copied straight from Debian. On Debian > /var/run/apache2 is the directory to put sockets in. > > You could try adding this configuration directive: > > > WSGISocketPrefix /var/run/apache2/wsgi > > -- > With kind regards, > Giel van Schijndel > - Interlink <www.il.fontys.nl> > > signature.asc > < 1KViewDownload -- 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.
