Utils/Tools all result in INVALID ARGUMENTS error on Debian 6. Libmemcached cannot connect by any means other than memcapable

Bug #1152612 reported by JmZ on 2013-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libmemcached
Undecided
Brian Aker

Bug Description

Have I simply configured memcached incorrectly or is this a bug?

I'm on Debian 6 with memcached 1.4.5 and libmemcached 1.0.10, along with libmemcached-tools.
If I start up memcached with the default debian config, it loads fine and the log remains completely empty.

If I then try run ANY libmemcached-tools binary against it *except* memcapable, they all fail with "INVALID ARGUMENTS".

memcapable -host 127.0.0.1

Works fine apart from "ascii verbosity" which times out.

I can telnet to memcached and execute commands directly just fine (e.g. stats).

# memcping --verbose --servers="127.0.0.1"
Failed to ping 127.0.0.1:11211 INVALID ARGUMENTS

This is the same for all commands. This also means PHP5 is unable to connect as it uses libmemcached.

Also tested with latest memcached and libmemcached.

Brian Aker (brianaker) wrote :

When you telnet, do you telnet to 127.0.0.1, or localhost?

Changed in libmemcached:
assignee: nobody → Brian Aker (brianaker)
JmZ (jmzrlz) wrote :

Both work fine.

Posted to mailing list a few days ago with an update.
A strace shows it can't even create the socket, never mind connect
Don't have the strace output on me, will have to dig it out of the mail list.

Also this is a production server so I updated to the testing release (wheezy) and now all is well. So I can't do further testing but there's definitely issues on squeeze.

Brian Aker (brianaker) wrote :

Check out 1.0.17

Changed in libmemcached:
status: New → Incomplete
Jason V. Miller (jmiller-d) wrote :

Curious... did something change in 1.0.17 related to INVALID ARGUMENTS?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers