Issue 251 in memcached: Failed to startup/connect to memcached server. at t/00-startup.t

[memc...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 251 by ma...@eatlime.com: Failed to startup/connect to memcached
server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

Making RPM from source as hightlighted on site:
yum -y install rpmdevtools gcc make
adduser makerpm
su makerpm
cd ~
rpmdev-setuptree
wget http://memcached.googlecode.com/files/memcached-1.4.13.tar.gz
rpmbuild -ta memcached-1.4.13.tar.gz

Returns such error:
t/00-startup.t ....... 1/18 getaddrinfo(): Name or service not known
failed to listen on TCP port 32473: Success
t/00-startup.t ....... 7/18
# Failed test '-b works'
# at t/00-startup.t line 37.
# got: 'Failed to startup/connect to memcached server. at
t/00-startup.t line 33
# '
# expected: ''
t/00-startup.t ....... 8/18
...........
and later:
...........
Invalid value for binding protocol: http
-- should be one of auto, binary, or ascii
t/00-startup.t ....... 16/18 Number of threads must be greater than 0
t/00-startup.t ....... 17/18 # Looks like you planned 18 tests but ran 17.
# Looks like you failed 1 test of 17 run.

OS: RHEL 6.1

[memc...@googlecode.com]

Comment #1 on issue 251 by dorma...@rydia.net: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

Can you include the output of a normal compile sequence?

ie;

tar -zxvf etc.tar.gz ; cd etc ; ./configure && make && make test

.13 definitely passes tests on 64bit centos6, but I haven't tried building
rpms with it.

[memc...@googlecode.com]

Comment #2 on issue 251 by ma...@eatlime.com: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

Here is output of compilation and "make test":

RHEL 6.1: PASSED

CentOS 5.5:
t/00-startup.t ....... 16/18
# Failed test 'binary works'
# at t/00-startup.t line 69.
# got: 'Failed to startup/connect to memcached server. at
t/00-startup.t line 67
# '
# expected: ''

Invalid value for binding protocol: http
-- should be one of auto, binary, or ascii

t/00-startup.t ....... 17/18 Number of threads must be greater than 0
t/00-startup.t ....... 18/18 # Looks like you failed 1 test of 18.
Timeout.. killing the process
t/00-startup.t ....... Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/18 subtests
t/64bit.t ............ ok
t/binary-get.t ....... ok
t/binary-sasl.t ...... This server is not built with SASL support.
t/binary-sasl.t ...... ok
t/binary.t ........... ok
t/bogus-commands.t ... ok
t/cas.t .............. Failed to startup/connect to memcached server. at
t/cas.t line 10
# Looks like your test exited with 111 before it could output anything.

[memc...@googlecode.com]

Comment #3 on issue 251 by dorma...@rydia.net: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

can you run:

$ prove -v t/00-startup.t and include the full output as an attachment?

[memc...@googlecode.com]

Comment #4 on issue 251 by ma...@eatlime.com: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

In attachement there are two output files from CentOS 5.5 and RHEL 6.1

Attachments:
output CentOS 5.5.txt 26.2 KB
output RHEL 6.1.txt 503 KB

[memc...@googlecode.com]

Comment #5 on issue 251 by sev...@gmail.com: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

Hello.
Is there any update about this ticket?

Thanks.

[memc...@googlecode.com]

Comment #6 on issue 251 by dorma...@rydia.net: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

I think you've done something weird with your install directory under
centos5.

I have centos5 instances (32bit/64bit) and they don't do this.

It looks like you did part of the compile as root, but are still using the
same directory?

If you untar 1.4.13 into a fresh directory, and manually run "./configure
&& make && make test" everything should work fine.

[memc...@googlecode.com]

Updates:
Status: Fixed

Comment #7 on issue 251 by dorma...@rydia.net: Failed to startup/connect to

memcached server. at t/00-startup.t
http://code.google.com/p/memcached/issues/detail?id=251

Haven't heard back from my last post... assuming user figured it out? If
not, please reopen with the report on what I'd mentioned to try.