On 25 June 2010 06:16, Dan Kamins <[email protected]> wrote:
> Resurrecting this old thread about these errors spamming in the error log all 
> the time:
>
> Exception KeyError: KeyError(47435225036128,) in <module 'threading' from 
> '/usr/local/lib/python2.6/threading.pyc'> ignored
> Exception KeyError: KeyError(47435225036128,) in <module 'threading' from 
> '/usr/local/lib/python2.6/threading.pyc'> ignored
> Exception KeyError: KeyError(47435225036128,) in <module 'threading' from 
> '/usr/local/lib/python2.6/threading.pyc'> ignored

If you are using daemon mode, and not using embedded mode at all, have you set:

  WSGIRestrictEmbedded On

This will get rid of most of these messages where they relate to
Apache server child processes. See:

  http://blog.dscpl.com.au/2009/11/save-on-memory-with-modwsgi-30.html

It is assumed you are using mod_wsgi 3.X.

> Is your suggested fix included in the official mod_wsgi release yet?

Only in subversion. There has been no reason to come out with a new
2.X/3.X version as no serious issues have come up.

> Or any other fix that would address this issue?

There is no other fix. The alternatives are a pain as have to modify
the run time behaviour of mod_wsgi based on patch revision of Python.

> Or any updates to Python itself that addresses this?

There is nothing they can do now. They already made made the arguable
mistake of changing observable C API behaviour in a patch revision
rather than new minor version where compile time checks can be made,
thus the genie is out of the bottle and they cant go back.

Graham

> Since this was apparently a "harmless" (but very annoying) error, we have 
> been living with it...
>
> Thank you.
>
> dk
>
>
> On Apr 16, 2010, at 5:35 AM, Graham Dumpleton wrote:
>
>> If keen to get rid of the KeyError message in logs, add the following
>> two lines just before the call to Py_Finalize() in mod_wsgi.c code.
>>
>>    if (!PyImport_AddModule("dummy_threading"))
>>        PyErr_Clear();
>>
>> Note that the error in the logs is harmless. These two lines just get
>> rid of it by devious means rather than adding a run time check as to
>> whether Python 2.6.5+ or Python 3.1.2+ is being used.
>>
>> 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.
>
>

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

Reply via email to