I actually did read up on all the issues docs & tried to use the plausible
solutions as well.
In the ended up creating a folder in "/var/run/apache2" for the socket
files. And then changing permissions to 755 & then doing chown. I know that
this is not the ideal solution & if I had more time then I would have done
what Graham D. suggested in this
thread.<http://groups.google.com/group/modwsgi/browse_thread/thread/795d653659a97f34/d2a4cf735b8071ab?lnk=gst&q=slackware#d2a4cf735b8071ab>

But Thanks guys for the help.

On Thu, Oct 14, 2010 at 11:36 AM, Carl Nobile <carl.nob...@gmail.com> wrote:

> Below is a link to the docs where Graham gives some solutions to this
> issue.
>
>
> http://code.google.com/p/modwsgi/wiki/ConfigurationIssues#Location_Of_UNIX_Sockets
>
> ~Carl
>
> On Thu, Oct 14, 2010 at 10:32 AM, Graham Dumpleton
> <graham.dumple...@gmail.com> wrote:
> >
> >
> > It is ability of Apache user to read files created, not write them. When
> being created the process is run as root, so no problem at that point.
> >
> > That error can occur for other reasons as well.
> >
> > On really bad Internet from my phone  right now, so can't elaborate.
> >
> > On 14/10/2010, at 9:19 PM, Carl Nobile <carl.nob...@gmail.com> wrote:
> >
> >> I have seen this issue before it is usually caused by permission
> >> changes in the path leading to the socket file. You can test this by
> >> setting the socket file to be put into /tmp. If it starts to work
> >> correctly check the path to the old location and be sure apache can
> >> write to every directory in it.
> >>
> >> ~Carl
> >>
> >> On Wed, Oct 13, 2010 at 7:30 PM, Chintan Tank <tankchin...@gmail.com>
> wrote:
> >>> Since past 2 days I have been getting the following error -
> >>>
> >>> (2)No such file or directory: mod_wsgi (pid=2709): Unable to connect
> >>> to WSGI daemon process 'my_site' on '/var/run/apache2/wsgi.
> >>> 2688.2.1.sock' after multiple attempts.
> >>>
> >>> Since it was working before, I dont know why the error has been
> >>> caused. I have tried following without success -
> >>>
> >>>   1. Providing WSGISocketPrefix
> http://www.mail-archive.com/python-l...@python.org/msg180917.html
> >>>   2. Kill all the apache daemons manually & then restarting the
> >>> server.
> >>>   3. I have made sure that the mod_wsgi exists in the location
> >>> pointed to in the httpd.conf
> >>>
> >>> Any help or pointers towards this will be great.
> >>>
> >>> I am at my wit's end, especially this was working just 2 days back & I
> >>> cant recall making any system updates. Not sure if this is relevant
> >>> but I did run apache & django dev server on this machine. But mostly
> >>> never in parallel.
> >>>
> >>> P.S. My httpd.conf snippet
> >>>
> >>> WSGIDaemonProcess my_site python-path=/usr/local/code/pinax/pinax-env/
> >>> lib/python2.6/site-packages threads=25 user=daemon group=daemon
> >>> WSGIProcessGroup my_site
> >>>
> >>>
> >>> WSGIScriptAlias / /usr/local/code/my_site/deploy/pinax.wsgi
> >>> #WSGISocketPrefix /var/run/apache2/wsgi
> >>>
> >>>
> >>> <Directory /usr/local/code/my_site/deploy>
> >>>    Order deny,allow
> >>>    Allow from all
> >>> </Directory>
> >>>
> >>> <Directory /usr/local/my_site_db>
> >>>    Order deny,allow
> >>>    Allow from all
> >>> </Directory>
> >>>
> >>> Please help.
> >>>
> >>> --
> >>> You received this message because you are subscribed to the Google
> Groups "modwsgi" group.
> >>> To post to this group, send email to modw...@googlegroups.com.
> >>> To unsubscribe from this group, send email to
> modwsgi+unsubscr...@googlegroups.com<modwsgi%2bunsubscr...@googlegroups.com>
> .
> >>> For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >>
> -------------------------------------------------------------------------------
> >> Carl J. Nobile (Software Engineer)
> >> carl.nob...@gmail.com
> >>
> -------------------------------------------------------------------------------
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups "modwsgi" group.
> >> To post to this group, send email to modw...@googlegroups.com.
> >> To unsubscribe from this group, send email to
> modwsgi+unsubscr...@googlegroups.com<modwsgi%2bunsubscr...@googlegroups.com>
> .
> >> 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 modw...@googlegroups.com.
> > To unsubscribe from this group, send email to
> modwsgi+unsubscr...@googlegroups.com<modwsgi%2bunsubscr...@googlegroups.com>
> .
> > For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
> >
> >
>
>
>
> --
>
> -------------------------------------------------------------------------------
> Carl J. Nobile (Software Engineer)
> carl.nob...@gmail.com
>
> -------------------------------------------------------------------------------
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To post to this group, send email to modw...@googlegroups.com.
> To unsubscribe from this group, send email to
> modwsgi+unsubscr...@googlegroups.com<modwsgi%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
>
>


-- 
Thanks & Regards,

Chintan Tank
Software Developer
School of Library & Information Science
Indiana University, Bloomington.

http://www.cs.indiana.edu/~cdtank/

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to modw...@googlegroups.com.
To unsubscribe from this group, send email to 
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to