Issue 120 in memcached: Failed to write, and not due to blocking: Resource temporarily unavailable
memc...@googlecode.com
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 120 by saroo2603: Failed to write, and not due to blocking:
Resource temporarily unavailable
http://code.google.com/p/memcached/issues/detail?id=120
I have installed microsoft firewall client 4.0.3442 on my windows machine.
After this installation I am continuously getting the error "Lost connect
to localhost:11211"
On starting memcached server in verbose mode I get the following:
slab class 37: chunk size 286872 perslab 3
slab class 38: chunk size 358592 perslab 2
slab class 39: chunk size 448240 perslab 2
<1228 server listening
<1216 new client connection
<1216 get session:84da1b8d07e27e73a30c648ddf8020c6
> 1216 END
Failed to write, and not due to blocking: Resource temporarily unavailable
<1216 connection closed.
<1196 new client connection
<1196 get session:29259496c8829c703ee21b5d1310bc28
> 1196 END
Failed to write, and not due to blocking: Resource temporarily unavailable
<1196 connection closed.
Product version used is 1.2.4 on Windows XP
Note: If i uninstall firewall client the connect is getting established
properly. Can anyone please tell why firewall installation is causing a
problem. How do I resolve this issue?
Thanks,
Surbhi.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
memc...@googlecode.com
Status: Invalid
Comment #1 on issue 120 by dorma...@rydia.net: Failed to write, and not due
to blocking: Resource temporarily unavailable
http://code.google.com/p/memcached/issues/detail?id=120
Closing this as it isn't a bug.
Please tune your firewall settings; you could be running into a limit of
concurrent
connections, or timing out connections early, or doing some sort of connect
rate
limiting. Use the support for your firewall product.