Description of problem: Getting following error messages in apache's error_log. Appearing these during repo sync. I guess these errors are not breaking anything but looks ugly with lots of errors. [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored [Wed Jul 27 19:11:34 2011] [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored Version-Release number of selected component (if applicable): pulp 0.214 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: [error] Exception KeyError: KeyError(140114289027040,) in <module 'threading' from '/usr/lib64/python2.6/threading.pyc'> ignored Expected results: Shouln't be any exception error in error_log Additional info:
These error messages are (supposedly) harmless, but are a result of mod_wsgi's behaviour. Qoute from Graham Dumpleton in the upstream bug: http://code.google.com/p/modwsgi/issues/detail?id=197 Comment 5 by project member Graham.Dumpleton, Apr 16, 2010 The message is harmless. Fix added in revision 1588 of subversion trunk for mod_wsgi 4.0 to get rid of it anyway.