jvandal / modwsgi

Automatically exported from code.google.com/p/modwsgi
0 stars 0 forks source link

Touching .wsgi file doesn't force reloading #161

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. I'm using Apache + mod_wsgi + django to serve our web application
2. I make some changes to source code of Django application
3. I `touch` wsgi file. I also tried open it with vi and save it with ":w" 
command

What is the expected output? What do you see instead?
I expect that next web-request will be served by the newest version of 
application. Instead the previous version continues working until apache 
restart

What version of the product are you using? On what operating system?
CentOS 4, Python 2.3.4, Apache 2.0.52

Please provide any additional information below.
I have daemon mode activated:
LoadModule wsgi_module modules/mod_wsgi.so
WSGISocketPrefix run/wsgi
<VirtualHost ip.ip.ip.ip>
...
   WSGIDaemonProcess chess threads=1 processes=10
   WSGIProcessGroup chess

   AliasMatch (.*)(\.gif|css|png|jpe?g|html)$ /var/www/vhosts/wellchess$1$2
   WSGIScriptAlias / /var/www/vhosts/wellchess/chess.wsgi/chess/
</VirtualHost>

When i look at error_log, is see Attach interpreter, Terminating Python, 
Cleanup interpreter in a cycle
[Sat Oct 17 04:43:39 2009] [info] mod_wsgi (pid=1366): Attach interpreter 
''.
[Sat Oct 17 04:43:40 2009] [info] mod_wsgi (pid=1367): Attach interpreter 
''.
[Sat Oct 17 04:43:40 2009] [info] mod_wsgi (pid=1368): Attach interpreter 
''.
[Sat Oct 17 04:43:41 2009] [info] mod_wsgi (pid=1371): Attach interpreter 
''.
[Sat Oct 17 04:43:41 2009] [info] mod_wsgi (pid=1372): Attach interpreter 
''.
[Sat Oct 17 04:43:41 2009] [info] mod_wsgi (pid=1369): Attach interpreter 
''.
[Sat Oct 17 04:43:41 2009] [info] mod_wsgi (pid=1370): Attach interpreter 
''.
[Sat Oct 17 04:43:44 2009] [info] mod_wsgi (pid=1375): Attach interpreter 
''.
[Sat Oct 17 04:43:45 2009] [info] mod_wsgi (pid=1262): Cleanup interpreter 
''.
[Sat Oct 17 04:43:45 2009] [info] mod_wsgi (pid=1262): Terminating Python.
[Sat Oct 17 04:43:46 2009] [info] mod_wsgi (pid=1273): Cleanup interpreter 
''.
[Sat Oct 17 04:43:46 2009] [info] mod_wsgi (pid=1273): Terminating Python.
[Sat Oct 17 04:43:47 2009] [info] mod_wsgi (pid=1146): Cleanup interpreter 
''.
[Sat Oct 17 04:43:47 2009] [info] mod_wsgi (pid=1146): Terminating Python.
[Sat Oct 17 04:43:48 2009] [info] mod_wsgi (pid=1343): Cleanup interpreter 
''.
[Sat Oct 17 04:43:48 2009] [info] mod_wsgi (pid=1343): Terminating Python.
[Sat Oct 17 04:43:50 2009] [info] mod_wsgi (pid=1377): Attach interpreter 
''.

Original issue reported on code.google.com by Best.I...@gmail.com on 17 Oct 2009 at 9:52

GoogleCodeExporter commented 8 years ago
Set:

  LogLevel info

to enable additional debugging information in Apache error logs.

Ensure you read:

  http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode

and use the test programs in there to validate that your application is indeed 
running in daemon mode.

State which version of mod_wsgi you are using and if not using latest, then 
upgrade.

You definitely should not be using mod_wsgi 1.X as the process reloading 
feature is not present in those older 
versions.

Original comment by Graham.Dumpleton@gmail.com on 17 Oct 2009 at 10:28

GoogleCodeExporter commented 8 years ago
Sorry, i have some misunderstood with server admin.
We have downloaded mod_wsgi 2.6 source, but installed mod_wsgi from repo via 
yum. 
That's why we got an old 1.3 version.

The issue can be closed.

Original comment by Best.I...@gmail.com on 19 Oct 2009 at 6:59

GoogleCodeExporter commented 8 years ago

Original comment by Graham.Dumpleton@gmail.com on 19 Oct 2009 at 9:51