Hi. do to solve this problem:
# yum update mod_wsgi
Em sexta-feira, 9 de abril de 2010 01h46min11s UTC-3, tmdk escreveu:
>
> I have a Django app running that *appears* to work fine (from a user's
> perspective). But the error_log is constantly filled with these
> threading KeyErrors (see below).
Sorry, mod_wsgi 3.3 is minimum to get rid of that warning. Not 3.0.
Graham
On 26 February 2013 03:40, Joel Taylor wrote:
> Hmmm, that's weird, I'm running Python 2.6.6 & mod_wsgi 3.2
>
> cat /var/log/httpd/error_log | grep mod_wsgi
>
> [Sun Feb 24 03:56:43 2013] [warn] mod_wsgi: Compiled for P
Oh, it looks like we need to upgrade to
3.3? https://code.google.com/p/modwsgi/wiki/ChangesInVersion0303
On Wednesday, February 13, 2013 3:51:53 PM UTC-6, Graham Dumpleton wrote:
>
> You should be upgrading mod_wsgi from version 2.8. Simple as that.
>
> So long as you aren't using mod_wsgi 3.X, y
Hmmm, that's weird, I'm running Python 2.6.6 & mod_wsgi 3.2
cat /var/log/httpd/error_log | grep mod_wsgi
[Sun Feb 24 03:56:43 2013] [warn] mod_wsgi: Compiled for Python/2.6.2.
[Sun Feb 24 03:56:43 2013] [warn] mod_wsgi: Runtime using Python/2.6.6.
[Sun Feb 24 03:56:43 2013] [notice] Apache/2.2.15
You should be upgrading mod_wsgi from version 2.8. Simple as that.
So long as you aren't using mod_wsgi 3.X, you will see this message.
Graham
On 14 February 2013 05:06, Kellen Fox wrote:
> I can confirm that this issue is still present in python 2.7.3 as well
>
>
> On Thursday, April 8, 2010
I can confirm that this issue is still present in python 2.7.3 as well
On Thursday, April 8, 2010 9:46:11 PM UTC-7, tmdk wrote:
>
> I have a Django app running that *appears* to work fine (from a user's
> perspective). But the error_log is constantly filled with these
> threading KeyErrors (see b
Last night we installed mod_wsgi 3.3, and the KeyErrors have totally
disappeared. I highly recommend the 3.3 upgrade if you're having this
problem. Thanks, Graham.
dk
On Jun 24, 1:16 pm, Dan Kamins wrote:
> Resurrecting this old thread about these errors spamming in the error log all
> the t
On 25 June 2010 06:16, Dan Kamins wrote:
> Resurrecting this old thread about these errors spamming in the error log all
> the time:
>
> Exception KeyError: KeyError(47435225036128,) in '/usr/local/lib/python2.6/threading.pyc'> ignored
> Exception KeyError: KeyError(47435225036128,) in '/usr/lo
Resurrecting this old thread about these errors spamming in the error log all
the time:
Exception KeyError: KeyError(47435225036128,) in ignored
Exception KeyError: KeyError(47435225036128,) in ignored
Exception KeyError: KeyError(47435225036128,) in ignored
Is your suggested fix included in
Hi Graham,
> I still don't see that as related. Having checked through the Python
> 2.6.5 code, the KeyError message is noise only and not indicative of a
> serious problem.
Just to let you know that you were right and the crashes were not related to
this mod_wsgi issue.
Cheers,
Thijs
--
You
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 devio
On 13 April 2010 18:36, Thijs Triemstra | Collab wrote:
> I opened a ticket yesterday
> (http://code.google.com/p/modwsgi/issues/detail?id=197) and I'm also looking
> forward to any updates. My brand new cloud server with 3GB of RAM is brought
> to it's knees after about 12 hours and I think it's
I opened a ticket yesterday
(http://code.google.com/p/modwsgi/issues/detail?id=197) and I'm also looking
forward to any updates. My brand new cloud server with 3GB of RAM is brought to
it's knees after about 12 hours and I think it's due to this mod_wsgi / Python
2.6.5 bug. That machine dies wi
FWIW, this is the problem they were trying to fix when making the changes.
http://bugs.python.org/issue1722344
Graham
On 13 April 2010 11:38, Dan Kamins wrote:
> Great to hear. We're still running with (and concerned about) this config,
> so as soon as you have more information, please do upd
Great to hear. We're still running with (and concerned about) this config, so
as soon as you have more information, please do update the list.
On Apr 12, 2010, at 6:29 PM, Graham Dumpleton wrote:
> Hooray, I have an environment set up where have been able to duplicate
> this now. :-)
>
> 2010
Hooray, I have an environment set up where have been able to duplicate
this now. :-)
2010/4/10 Evren Esat Özkan :
> I'm getting same errors on CentOS with mod_wsgi-3.2, Python-2.6.5,
> Django trunk. But my site working anyway...
>
>
> WSGIDaemonProcess .. processes=10 threads=10 inactivit
I'm getting same errors on CentOS with mod_wsgi-3.2, Python-2.6.5,
Django trunk. But my site working anyway...
WSGIDaemonProcess .. processes=10 threads=10 inactivity-
timeout=2000 maximum-requests=1000
[Fri Apr 09 18:10:09 2010] [error] Exception KeyError:
KeyError(-1209010416,) in
17 matches
Mail list logo
