Problem with new version memcached-1.4.24

[ali88code]

I have installed memcached ,php-pecl-memcached and libmemcached.
1.memcached (1.4.24)
2.php5.5.30 , php-pecl-memcached (2.2.0)
3.libmemcached(1.0.18)

I try with php script test.php

addServer('127.0.0.1',11211); $stats = $mc->getAllKeys(); echo "Return code:", $mc->getResultCode()."\n"; echo "Retucn Message:", $mc->getResultMessage () ."\n"; print_r ($stats); ?>

Return code:9
Retucn Message:CLIENT ERROR

I look the log on memcached server log
<36 stats cachedump 57 0
<36 stats cachedump 58 0
<36 stats cachedump 59 0
<36 stats cachedump 60 0
<36 stats cachedump 61 0
<36 stats cachedump 62 0
<36 stats cachedump 63 0

36 CLIENT_ERROR Illegal slab id
<36 quit
<36 connection closed.

I change to memcached version 1.4.15 ,and try php script test.php

Return code:0
Retucn Message:SUCCESS
Array
(
[0] => qinyao
[1] => andy
)

[scottchiefbaker]

I came here to report the same thing. This bug should be be changed from "Problem with new version memcached-1.4.24" to "getAllKeys() fails with result code 9" as it's more descriptive and will help the developer categorize things better.

I'm running PHP 7.0.5 and php-memcached compiled from git two months ago and I'm getting the same error.

getAllKeys() returns false
getResultCode() returns 9
getResultMessage() returns CLIENT ERROR

[DerDu]

Same here..

Error: 9 - CLIENT ERROR

PHP Version 7.0.4-7ubuntu2 (16.04 LTS, memcached 1.4.25)
php-memcached compiled from git today (24 May 2015, branch php7)

[billynoah]

Same problem here. If anyone has a workaround other than going to an older version of memcached please post.

[andrewnicols]

Still an issue on memcached 1.4.33.
It looks like this issue first appeared in 1.4.23.

Causes major issues for us.

[andrewnicols]

This is actually a bug in libmemcached: https://bugs.launchpad.net/libmemcached/+bug/1534062

[Mattie112]

Oh yes that bug, took quite some time to find that issue. If everybody can mark that issue as "this affects me" (top left) then I hope I will finally get a reply on it!

[andrewnicols]

Given the last release of libmemcached was two years ago, I'm not holding out much hope I admit :/

I've just proposed an alternate fix route, but I've not written c for many years so I'm unlikely to e able to work on this myself.

[Mattie112]

Well yes, I noticed that already when submitting that bug :p Still hoping that someday it will be fixed, for now using 1.4.22 just works fine for us.

[sodabrew]

Good find! We should be able to work around this in the client code php-memcached.

[nadavkav]

This causes major issues for us too.
Can any core developer confirm it and give any status about this?
It would be very much appreciated

[sodabrew]

@nadavkav #203 (comment)

[nadavkav]

@sodabrew , are you php-memcached core developer?

[sodabrew]

Yes, I'm a member of this repo. Sorry for the curt note, here's a longer explanation:

A quick read of the libmemcached code suggests that the CLIENT_ERROR status comes back from libmemcached after php-memcached has already processed the return data callbacks. I need to verify this, and then ignore the particular error in the event that we've already got data in-hand.

[nadavkav]

Great! thank you very much for the quick reply and explanation of the possible cause for this issue.

[Mattie112]

Ah great, I've only reported it at libmemcached, never thought of reporting it here :) But thanks!