You haven't explained how it is failing so is hard to say.

What actual URL are you using to access the site?

What is the error the browser returns?

Is 'yohost' a resolvable hostname?

Also see comments below.

On 25/09/2014, at 9:04 PM, David Sargrad <[email protected]> wrote:

> I am trying to follow the instructions for running the mod_wsgi hello world 
> application:
> https://code.google.com/p/modwsgi/wiki/WhereToGetHelp
> 
> I installed apache2 and libapache2-mod-wsgi
> sudo apt-get install apache2
> sudo apt-get install libapache2-mod-wsgi
> 
> My wsgi hello world:
> /var/www/yo/public_html# cat yo.wsgi
> def application(environ, start_response):
>     status = '200 OK'
>     output = 'Yo World!'
> 
>     response_headers = [('Content-type', 'text/plain'),
>                         ('Content-Length', str(len(output)))]
> 
>     start_response(status, response_headers)
> 
>     return [output]

As a general rule, if using WSGIScriptAlias, you should not be placing the WSGI 
script file in the DocumentRoot directory, especially where you have mounted it 
at a sub URL as the source code for the application is downloable via the 
DocumentRoot directory.

> 
> My virtualhost:
> /etc/apache2/sites-available# cat yo.conf
> <VirtualHost *:80>
>     ServerName yohost

Is 'yohost' a valid name which is resolvable?

> #    WSGIDaemonProcess cwpmash user=ubuntu group=ubuntu threads=5
>     WSGIScriptAlias /yo /var/www/yo/public_html/yo.wsgi

This indicates you should be access it as:

http://yohost/yo

>     DocumentRoot /var/www/yo/public_html

Because you are stick your code in DocumentRoot and mounting at sub URL, I can 
download the source code by accessing:

http://yohost/yo.wsgi

Thus why you shouldn't put it there.

>     <Directory /var/www/yo/public_html>
> #        WSGIProcessGroup cwpmash
> #        WSGIApplicationGroup %{GLOBAL}
>         Order allow,deny
>         Allow from all
>     </Directory>
> </VirtualHost>
> 
> I've enabled info logging in apache (rather than warn).
> 
> I've enabled the site:
> /etc/apache2/sites-available# ls ../sites-enabled/
> 000-default.conf  yo.conf
> 
> 
> 
> 
> My apache2 error log shows the following on apache restart:
> 
> [Thu Sep 25 13:04:46.211520 2014] [:info] [pid 2305:tid 139868472567680] 
> mod_wsgi (pid=2305): Destroying interpreters.
> [Thu Sep 25 13:04:46.211603 2014] [:info] [pid 2305:tid 139868472567680] 
> mod_wsgi (pid=2305): Cleanup interpreter ''.
> [Thu Sep 25 13:04:46.211907 2014] [:info] [pid 2306:tid 139868472567680] 
> mod_wsgi (pid=2306): Destroying interpreters.
> [Thu Sep 25 13:04:46.211976 2014] [:info] [pid 2306:tid 139868472567680] 
> mod_wsgi (pid=2306): Cleanup interpreter ''.
> [Thu Sep 25 13:04:46.216683 2014] [:info] [pid 2305:tid 139868472567680] 
> mod_wsgi (pid=2305): Terminating Python.
> [Thu Sep 25 13:04:46.217228 2014] [:info] [pid 2306:tid 139868472567680] 
> mod_wsgi (pid=2306): Terminating Python.
> [Thu Sep 25 13:04:46.220709 2014] [:info] [pid 2305:tid 139868472567680] 
> mod_wsgi (pid=2305): Python has shutdown.
> [Thu Sep 25 13:04:46.221243 2014] [:info] [pid 2306:tid 139868472567680] 
> mod_wsgi (pid=2306): Python has shutdown.
> [Thu Sep 25 13:04:46.226124 2014] [core:info] [pid 2302:tid 139868472567680] 
> AH00096: removed PID file /var/run/apache2/apache2.pid (pid=2302)
> [Thu Sep 25 13:04:46.226199 2014] [mpm_event:notice] [pid 2302:tid 
> 139868472567680] AH00491: caught SIGTERM, shutting down
> [Thu Sep 25 13:04:47.348730 2014] [mpm_event:notice] [pid 2484:tid 
> 140368719771520] AH00489: Apache/2.4.7 (Ubuntu) mod_wsgi/3.4 Python/2.7.6 
> configured -- resuming normal operations
> [Thu Sep 25 13:04:47.348963 2014] [mpm_event:info] [pid 2484:tid 
> 140368719771520] AH00490: Server built: Jul 22 2014 14:36:38
> [Thu Sep 25 13:04:47.349000 2014] [core:notice] [pid 2484:tid 
> 140368719771520] AH00094: Command line: '/usr/sbin/apache2'
> [Thu Sep 25 13:04:47.349215 2014] [:info] [pid 2487:tid 140368719771520] 
> mod_wsgi (pid=2487): Initializing Python.
> [Thu Sep 25 13:04:47.351673 2014] [:info] [pid 2488:tid 140368719771520] 
> mod_wsgi (pid=2488): Initializing Python.
> [Thu Sep 25 13:04:47.371271 2014] [:info] [pid 2487:tid 140368719771520] 
> mod_wsgi (pid=2487): Attach interpreter ''.
> [Thu Sep 25 13:04:47.372339 2014] [:info] [pid 2488:tid 140368719771520] 
> mod_wsgi (pid=2488): Attach interpreter ''.
> 
> 
> I'm sure the SIGTERM is not good, and perhaps is at the core of the problem. 
> This seems like a very simple configuration, yet I cant get it working. 
> Unfortunately the error log is not that informative, at least to an untrained 
> eye.

The SIGTERM message is normal. That is what you will see when Apache is being 
restarted.

> Please help. What am I doing wrong?

Need to know what is failing first before can guess.

Graham

-- 
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.

Reply via email to