Guys,
We are seeing tons of these messages reported;
Memcache::get(): Server 10.3.230.15 (tcp 11211) failed with:
Connection timed out (110)
They are reported on all six of our webservers. Memcache is working
but lots of connections are timing out as reported with the above
messages.
We are
Upgrade back to 1.4.5 and look for the 'listen_disabled_num' value in the
stats output. If the number is increasing, you're hitting maxconns.
If not, you're probably seeing packet loss, or have a firewall in the way
that's maxing out.
On Tue, 7 Sep 2010, the_fonz wrote:
Guys,
We are seeing
On 9/7/10 10:50 AM, the_fonz wrote:
We are running memcached 1.2.5 with php-pecl-memcache-2.2.3 (we also
tried with memcache 1.4.5 but had the same errors). We have PHP 5.2.6
running on x86 Hardware with Red Hat 5.5.
We have six web servers all running Apache 2.2 on prefork mode.
Prefork
Comment #13 on issue 60 by lind...@inuus.com: Compile error with gcc-4.4
http://code.google.com/p/memcached/issues/detail?id=60
Failing on Fedora 13, but only if you use -Wall
let me know if I should commit this patch to my tree so you can get a pull
request..
Sorry, my memcache knowledge is about two weeks old (am learning though!)
Do you mean are we pooling connections? No we are not.
PHP should just drop the connection once it's finished with it. there is no
timeout or close connection set within PHP.
Date: Tue, 7 Sep 2010 11:19:18 -0500
