I've seen this happen when you run out of connections as well. Check the value of the -c argument and make sure the number of connections your clients are creating is not exceeding the value set in the server.
On Sep 18, 2009, at 7:57 PM, Jeff wrote: I am running the Windows port of version 1.2.1, and I saw this when I first built the server. I was able to fix it by adding the following code in drive_machine, after getting the connection (line 1678 in the source I downloaded): newc->request_addr = addr; newc->request_addr_size = sizeof(addr); I'm happy to make my source or binary available to see if it helps, but it is a pretty old version. FWIW, it runs for days and days without crashing. On Wed, Sep 16, 2009 at 2:49 AM, Adi <[email protected]<mailto:[email protected]>> wrote: Hi, I have created a sample application by using BeIT.MemCached client to test memcached ver 1.2.5, it is working fine on my PC (Vista Professional) but when i access or want to store data from another PC (that is also on the same network) i faced this error: "Failed to write, and not due to blocking" Than i run the client application / server 1.2.5 on Windows Server 2003 and tried to Get the value from local memcached server but still the same problem persist. I have alsr tried MemCached ver 1.2.1 and 1.2.6, but the problem persist. Please let me know is this problem specific to client (BeIT) or Memcached Server. I have also red other post but didn't find the solution of this problem. Waiting for your reply. Adeel
