On 17/06/2014, at 11:33 PM, Tim Richardson <[email protected]> wrote:
> I have 32 bit Apache 2.4.9 compiled against VC9 running with ActiveState 32 > bit Python 2.7.6. I had to use the VC9 because this was only way I could get > pyodbc working. > The web application is web2py, running with the wsgi script coming with > web2py. > It constantly runs one core on the server at 100%, under no load. Actually, > every so often (say every five minutes) the pythonw executable dies, the CPU > load drops down to zero for about five seconds, and then returns to almost > full use of a core because pythonw is respawned. > > Memory load is stable and small (32 MB according to task manager). This is > on Windows server 2008 > The service description is > Apache/2.4.9 (Win32) OpenSSL/1.0.1h mod_wsgi/3.5 Python/2.7.6 > > The mod_wsgi is a downloaded from the recommended site, although it says it > is built against VC10. There are no errors logged by Apache. Interactive > response on the server seems ok. > > Previously I had almost this running on a 32 bit Windows Server 2003. It was > also Apache 2.4, but an earlier version. THe problem is reproduced by the > version of web2py that worked fine on the old server, so I think it is a > mod_wsgi problem with the new server, but I don't know where to look. There are a number of problems with what you are describing. The main one is that mod_wsgi embeds Python into Apache, there is no separate 'pythonw' process instance. This makes me wonder whether you are using or even needing mod_wsgi as it sounds like you are starting Web2Py separately via its own builtin server and perhaps only proxying to it via Apache. If that is the case you do not need mod_wsgi at all and any issue with the 'pythonw' process chewing up CPU or crashing entirely is a problem for the Web2Py folks to worry about. If for some reason your description is wrong and 'pythonw' isn't involved and you are actually running Web2Py inside of Apache with mod_wsgi, then then next issue is the mixing of VC9 and VC10 binaries. That is, a VC9 compiled Apache and a VC10 compiled Python installation and VC10 compiled mod_wsgi. I am not a Windows person, but would be extremely cautious about mixing binaries from different versions of the Microsoft compilers as not entirely sure you wouldn't have problems. Anyway, first up explain properly how you are starting Web2Py. Why is 'pythonw' factoring into this because if using mod_wsgi then it shouldn't. 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.
