What steps will reproduce the problem? 1. memcached -l ::1
What is the expected output? What do you see instead? - Expected is that memcached binds to the interface
- Actual result Invalid port number: ":1"failed to listen on TCP port 11211: Success
What version of the product are you using? On what operating system? 1.4.15 on Ubuntu 12.04
It does work in Debian 6.0 (memcached 1.4.5) but not with anything newer I tested...
Please provide any additional information below.
Comment #1
Posted on Feb 12, 2013 by Grumpy LionWork around is to use an IPv6 only DNS name as parameter to L
Comment #2
Posted on Dec 5, 2013 by Swift CamelHello,
The same issue. I can't bind an ipv6 address.
Please help.
Comment #3
Posted on Dec 5, 2013 by Swift CamelComment deleted
Comment #4
Posted on Jan 9, 2015 by Quick LionPull request https://github.com/memcached/memcached/pull/98
allows to specify IPv6 address without port or IPv6 address enclosed in [] with or without port (RFC3986 style recommended by RFC5952)
-l IPv6 -l [IPv6] -l [IPv6]:port
Comment #5
Posted on Feb 16, 2015 by Swift ElephantThis is a serious defect/flaw. When will it be fixed in an official release?
Comment #6
Posted on Feb 22, 2015 by Massive HippoSame problem here! I am unable to run memcached in a Dual-Stacked network environment!
Comment #7
Posted on Feb 22, 2015 by Swift LionI know that it's not really a solution and this still needs to be fixed, but running memcached on 127.0.0.1 and haproxy on external ip's with 127.0.0.1:11211 as a backend is a workaround. Op 22 feb. 2015 03:22 schreef :
Comment #8
Posted on May 6, 2015 by Massive HippoWhy it isn't a "real solution"? I'm planning to put this into production... Is it not recommended?
I REALLY need to bind memcached on an IPv6 address, since my networks are already IPv6-Only.
Status: New
Labels:
Type-Defect
Priority-Medium