NOTE: I am about to more or less go off the Internet for a week, don’t expect any responses from me after this for a bit.
The problem is occurring because the path to the socket file is too long: /Users/judith/blaze_dev/lib/python2.7/site-packages/mod_wsgi/server/mod_wsgi-express-80/wsgi.344.1.1.sock There is a limit on how long the path to a UNIX socket can be of 106 ish (from memory) characters. What I don’t understand is why that socket path it being set to be within your Python virtual environment or installation as it shouldn’t be unless you had gone and set sever root to be at the location: /Users/judith/blaze_dev/lib/python2.7/site-packages/mod_wsgi/server/mod_wsgi-express-80 Are you overriding the TMPDIR environment variable or have root dir being set to a location which in the path has a directory which is a symlink to this strange place? As to port 80 vs 8000, you are using two different ways of starting it and in one way you don’t tell it to use port 80 and so it defaults to port 8000. Which way do you want to use? Graham > On 2 Sep 2015, at 1:25 pm, Judith Boonstra <[email protected]> wrote: > > Getting permission denied error when trying to run a Django application from > another computer on the network. > > Log file: [Wed Sep 02 10:39:03.047752 2015] [wsgi:error] [pid 592] > (13)Permission denied: [client 10.0.1.24:54856] mod_wsgi (pid=592): Unable to > connect to WSGI daemon process 'localhost:80' on > '/Users/judith/blaze_dev/lib/python2.7/site-packages/mod_wsgi/server/mod_wsgi-express-80/wsgi.344.1.1.sock' > as user with uid=70., referer: http://laptop.local/admin > > Setup command seemed to run sucessfully: > > (blaze_dev)laptop:django judith$ python manage.py runmodwsgi --setup-only > --port=80 --user test --group test --server-root = > /var/run/blaze/mod_wsgi-express-80 > > Successfully ran command. > > Server URL : http://localhost/ > > Server Root : /Users/judith/blaze/django/= > > Server Conf : /Users/judith/blaze/django/=/httpd.conf > > Error Log File : /Users/judith/blaze/django/=/error_log (warn) > > Environ Variables : /Users/judith/blaze/django/=/envvars > > Control Script : /Users/judith/blaze/django/=/apachectl > > Request Capacity : 5 (1 process * 5 threads) > > Request Timeout : 60 (seconds) > > Queue Backlog : 100 (connections) > > Queue Timeout : 45 (seconds) > > Server Capacity : 20 (event/worker), 20 (prefork) > > Server Backlog : 500 (connections) > > Locale Setting : en_US.UTF-8 > > > > > > Start (and restart) server command & runmodwsgi command seemed fine: > > > > (blaze_dev)laptop:django judith$ sudo > /Users/judith/blaze_dev/lib/python2.7/site-packages/mod_wsgi/server/mod_wsgi-express-80/apachectl > restart > > Password: > > (blaze_dev)laptop:django judith$ python manage.py runmodwsgi > > Successfully ran command. > > Server URL : http://localhost:8000/ > > Server Root : /tmp/mod_wsgi-localhost:8000:501 > > Server Conf : /tmp/mod_wsgi-localhost:8000:501/httpd.conf > > Error Log File : /tmp/mod_wsgi-localhost:8000:501/error_log (warn) > > Request Capacity : 5 (1 process * 5 threads) > > Request Timeout : 60 (seconds) > > Queue Backlog : 100 (connections) > > Queue Timeout : 45 (seconds) > > Server Capacity : 20 (event/worker), 20 (prefork) > > Server Backlog : 500 (connections) > > > Locale Setting : en_US.UTF-8 > > > note: I am perplexed about the '8000'. Thought I would see '80' instead? > > > On the server system, entering localhost:8000/admin brings up the application > as expected. > Either on the server, or from another system within my network, entering the > ff coomand: laptop.local/admin, brings up the ff message: > > Service Unavailable > > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. Looking in the > error_log shows the error mentioned above. Please note that this same error > comes up in the 'laptop.local/admin' command is issued from the server. > > > > It should be noted I was very unsure about what to use for the user and group > names. In reading various info on the net, I see these names seem to have > been already defined for Unix systems. Tried to get more info about them for > the OS X operating environment, but was not successful. Should the names I > entered for user and group have already been defined. > > > > It should also be noted that I went through all the steps for setting up the > development environment, and everything seemed fine. In that case, I used > the ff commands > > > > mod_wsgi-express start server > > python manage.py runmodwsgi > > then entered laptop.local:8000/admin in my browser and the application came > up just fine. > > > > Would really appreciate some guidance. > > > > I must mention that mod_wsgi-express seems like a dream come true! I am > planning to use it instead of the Django development server if all goes well. > Thank you Graham! > > > > I seem so close, yet for far from having an operational environment! > > > > Thank you in advance for whatever advice you can provide. > > > > Judith Boonstra > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/modwsgi > <http://groups.google.com/group/modwsgi>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
