On 18 October 2010 22:57, Tarun Pasrija <[email protected]> wrote: > Graham, > > With respect to the post below which was going on earlier:- > http://groups.google.com/group/modwsgi/browse_thread/thread/e1e8e7b55760e992/fe6b046a6d9e34bb?lnk=gst&q=wsgi+script+timeout#fe6b046a6d9e34bb > > I am getting the same errors when I am on NFS shared. I did not have > much time since the code was going into production and thus tried to > downgrade to version 2.8 and it worked fine. I have also tried the > WSGIGroup alias and also tried using 3.3 but the same thing happened > still. > > Request you to please look into this since for the next release we > would like to move to mod_wsgi 3.3. It would be helpful if you can > repro the same scenario, else please let me know if you need any logs. > > I am running wsgi under daemon mode with apache MPM.
What are you expecting to be fixed? The outcome of that prior thread (error of 'daemon process deadlock timer expired') was that the issue was with a specific third party C extension module being used which is known not to work properly in Python sub interpreters and thus it was necessary to force mod_wsgi to run WSGI application in the main interpreter. This issue is documented in: http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Python_Simplified_GIL_State_API So, nothing to do with NFS and nothing to do with mod_wsgi itself. As would have been the situation with that prior case, there are no known differences between mod_wsgi between 2.X and 3.X which could cause existing code, using exact same versions of third party Python modules, to break. Thus, if it worked with 2.X, should have been okay with 3.X if same application code base. You will need to investigate your problem further, supply actual configuration used and the actual complete error messages from the Apache error log. Graham -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
