Failed too write, and not due to blocking

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

http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxeffqnlpkhwg+state:results

Does the above thread describe what you're trying to do? Are you using the
latest version of my client? Can you avoid using the CAS functionality?


/Henrik

On Wed, Sep 16, 2009 at 11:49, Adi <[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

Which version of BeIT memcached client should be used to resolve that
problem please give me its link, i have tried this:
http://code.google.com/p/beitmemcached/downloads/list

But had the same error.

Please let me know how to avoid CAS functionality? Does it mean Code
Access Security? that can be disable by using a command line "caspol -
s -off", tried this too and had the same behavior.


On Sep 16, 6:12 pm, Henrik Schröder <skro...@gmail.com> wrote:
> http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxe...
>
> Does the above thread describe what you're trying to do? Are you using the
> latest version of my client? Can you avoid using the CAS functionality?
>
> /Henrik
>
>
>
> On Wed, Sep 16, 2009 at 11:49, Adi <adeelna...@gmail.com> 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

I have check your reference post too, but it doesn't resolve the
problem, actually that post doesn't have a clear solution.

On Sep 16, 6:12 pm, Henrik Schröder <skro...@gmail.com> wrote:
> http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxe...
>
> Does the above thread describe what you're trying to do? Are you using the
> latest version of my client? Can you avoid using the CAS functionality?
>
> /Henrik
>
>
>
> On Wed, Sep 16, 2009 at 11:49, Adi <adeelna...@gmail.com> 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

That should be the latest version.

The error is some sort of internal error in memcached, and unfortunately I
have no idea what causes it, maybe the memcached developers can help? I know
I encountered it before when I accidentally caused some sort of resource
starvation, but for single gets across machines you should never, ever see
it. We've been running memcached on Windows Server 2003 and 2008, XP, Vista
and Windows 7 without ever getting that problem.


/Henrik

On Thu, Sep 17, 2009 at 07:30, Adi <[email protected]> wrote:

>
> Which version of BeIT memcached client should be used to resolve that
> problem please give me its link, i have tried this:
> http://code.google.com/p/beitmemcached/downloads/list
>
> But had the same error.
>
> Please let me know how to avoid CAS functionality? Does it mean Code
> Access Security? that can be disable by using a command line "caspol -
> s -off", tried this too and had the same behavior.
>
>
> On Sep 16, 6:12 pm, Henrik Schröder <skro...@gmail.com> wrote:
> > http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxe....
> >
> > Does the above thread describe what you're trying to do? Are you using
> the
> > latest version of my client? Can you avoid using the CAS functionality?
> >
> > /Henrik
> >
> >
> >
> > On Wed, Sep 16, 2009 at 11:49, Adi <adeelna...@gmail.com> 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
>

You could also try one of the other .Net clients to see if the problem
persists, and you should try other combinations of machines. You should also
try to just telnet to the memcached server from different machines and issue
some simple commands and see if you still get the error.


/Henrik

On Thu, Sep 17, 2009 at 11:48, Henrik Schröder <[email protected]> wrote:

> That should be the latest version.
>
> The error is some sort of internal error in memcached, and unfortunately I
> have no idea what causes it, maybe the memcached developers can help? I know
> I encountered it before when I accidentally caused some sort of resource
> starvation, but for single gets across machines you should never, ever see
> it. We've been running memcached on Windows Server 2003 and 2008, XP, Vista
> and Windows 7 without ever getting that problem.
>
>
> /Henrik
>
>
> On Thu, Sep 17, 2009 at 07:30, Adi <[email protected]> wrote:
>
>>
>> Which version of BeIT memcached client should be used to resolve that
>> problem please give me its link, i have tried this:
>> http://code.google.com/p/beitmemcached/downloads/list
>>
>> But had the same error.
>>
>> Please let me know how to avoid CAS functionality? Does it mean Code
>> Access Security? that can be disable by using a command line "caspol -
>> s -off", tried this too and had the same behavior.
>>
>>
>> On Sep 16, 6:12 pm, Henrik Schröder <skro...@gmail.com> wrote:
>> > http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxe.
>> ..
>> >
>> > Does the above thread describe what you're trying to do? Are you using
>> the
>> > latest version of my client? Can you avoid using the CAS functionality?
>> >
>> > /Henrik
>> >
>> >
>> >
>> > On Wed, Sep 16, 2009 at 11:49, Adi <adeelna...@gmail.com> 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
>>
>
>

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]> 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

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

Can someone send me the Memcached server, working binaries and client that
works perfectly on Windows Server 2003, i tried different version of Clients
but the same problem persist.



On Mon, Sep 21, 2009 at 5:40 PM, Brian Adams <[email protected]> wrote:

> 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]> 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
>
>
>
>


--
Adeel Ahmed
Project Coordinator
Softech Worldwide LLC
Cell: 0345-2136696

Closing the loop on this thread. I sent Adeel my Windows binaries, which
have a fix for the "Failed oo write, and not due to blocking" problem, and
he reports it's working for him.

On Thu, Sep 24, 2009 at 12:58 AM, Adeel Ahmed <[email protected]> wrote:

> Can someone send me the Memcached server, working binaries and client that
> works perfectly on Windows Server 2003, i tried different version of Clients
> but the same problem persist.
>
>
>
> On Mon, Sep 21, 2009 at 5:40 PM, Brian Adams <[email protected]> wrote:
>
>> 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]> 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
>>
>>
>>
>>
>
>
> --
> Adeel Ahmed
> Project Coordinator
> Softech Worldwide LLC
> Cell: 0345-2136696
>
>