On Tue, Jul 26, 2011 at 2:29 PM, het.oosten <het.oos...@gmail.com> wrote: > On the memcached mailing list they suspected this is a Django/python > issue so I started a thread here. A user named dormando replied that > the problem below looks like a connection failure (sock has gone null) > > I use memcached on a low traffic website with Django 1.2.4. Sometimes > I get this error message in my mail (full error below):
This looks like it's more likely to be an issue with the Python wrapper to memcache that you are using, rather than an issue with Django. Although the stack trace occurs as a result of Django calling the memcache API, the call is a simple get, and it's the internals of memcache.py that are failing. Django doesn't do any socket-level manipulation of memcache, and that appears to be where the problem lies. It looks like you're using the native Python wrapper around memcached; is this correct? If so, what version of the Python memcache library are you using? Have you tried updating to the latest version? Have you tried using PyLibMC instead? Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
