> We're using memcached to cache content generated by another > application on the same server. Items that are cached are set to never > expire, as the application currently self decides when it will refresh > items already in the cache. > > We run memcache with verbose output, and I occasionally see these one > or more entries in stderr: > > Couldn't realloc input buffer > > Sometimes, the memcached process will disappear, though I am not > seeing anything about that in the stderr/stdout output, other than the > message above. Sometimes there can be multiple realloc error messages > in stderr with memcached still running. > > It would appear that these issues only start creeping up once memcache > has reached its full capacity and starts evicting old entries. by > then, pyblibmc (which uses libmemcached) also occasionally produces > these errors: > > ProtocolError: error 8 from memcached_set: PROTOCOL > ERROR > WriteError: error 5 from memcached_set: WRITE > FAILURE > > Restarting memcached will stop the flow of errors until its full > capacity has been reached. > > We run memcached as follows: > > memcached -v -l 127.0.0.1:11211 -d -m 1024 -c 2000 -P /home/user/var/ > run/memcached.pid > > We're running version 1.4.10 on a debian lenny virtual server (OpenVZ) > on a RedHat 5.4 host (all 32-bits) > > Memcached is run with ulimit -v 3145728 and ulimit -n 2048 > > On average, it has only about 10 active connections. Stats output (of > an instance that is currently showing these errors):
Can you try 1.4.9? You may also be low on system memory. If downgrading doesn't work, reduce the memory limit from -m
