[ProFTPD-committers] [Bug 3657] "make check" raises two failures

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3657

--- Comment #1 from Bernd Lommerzheim <***@lommerzheim.com> 2011-05-19 04:26:57 EDT ---
Created attachment 3619
--> http://bugs.proftpd.org/attachment.cgi?id=3619
api-tests.log with two failures

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3657

--- Comment #2 from Bernd Lommerzheim <***@lommerzheim.com> 2011-05-19 06:29:04 EDT ---
$ proftpd -V (without --enable-tests)
Compile-time Settings:
Version: 1.3.4rc3 (CVS)
Platform: LINUX [Linux 2.6.32.40 x86_64]
Built: Do Mai 19 2011 09:51:20 CEST
Built With:
configure '--prefix=/usr' '--build=x86_64-pc-linux-gnu'
'--host=x86_64-pc-linux-gnu' '--mandir=/usr/share/man'
'--infodir=/usr/share/info' '--datadir=/usr/share' '--sysconfdir=/etc'
'--localstatedir=/var/lib' '--libdir=/usr/lib64'
'--localstatedir=/var/run/proftpd' '--sysconfdir=/etc/proftpd'
'--disable-strip' '--disable-facl' '--disable-auth-file' '--enable-cap'
'--disable-ident' '--enable-ipv6' '--disable-memcache' '--enable-ncurses'
'--enable-nls' '--disable-auth-pam' '--enable-pcre' '--disable-trace'
'--enable-shadow' '--enable-autoshadow' '--enable-openssl'
'--with-modules=mod_sql:mod_sql_passwd:mod_sql_mysql:mod_sftp:mod_sftp_sql'
'build_alias=x86_64-pc-linux-gnu' 'host_alias=x86_64-pc-linux-gnu'
'CFLAGS=-march=k8 -msse -msse2 -msse3 -O2 -pipe -fomit-frame-pointer'
'LDFLAGS=-Wl,-O1 -Wl,--as-needed' 'LIBS='

CFLAGS: -march=k8 -msse -msse2 -msse3 -O2 -pipe -fomit-frame-pointer -Wall
LDFLAGS: -L$(top_srcdir)/lib -Wl,-O1 -Wl,--as-needed -L/usr/lib64/mysql
LIBS: -lpcreposix -lpcre -lssl -lcrypto -lssl -lcrypto -lcap -lm
-lmysqlclient -lcrypto -lsupp -lcrypt -ldl -ldl -lz

Files:
Configuration File:
/etc/proftpd/proftpd.conf
Pid File:
/var/run/proftpd/proftpd.pid
Scoreboard File:
/var/run/proftpd/proftpd.scoreboard

Features:
+ Autoshadow support
- Controls support
+ curses support
- Developer support
- DSO support
+ IPv6 support
+ Largefile support
- Lastlog support
- Memcache support
+ ncursesw support
+ NLS support
+ OpenSSL support
+ PCRE support
- POSIX ACL support
+ Shadow file support
+ Sendfile support
- Trace support

Tunable Options:
PR_TUNABLE_BUFFER_SIZE = 1024
PR_TUNABLE_DEFAULT_RCVBUFSZ = 8192
PR_TUNABLE_DEFAULT_SNDBUFSZ = 8192
PR_TUNABLE_GLOBBING_MAX_MATCHES = 100000
PR_TUNABLE_GLOBBING_MAX_RECURSION = 8
PR_TUNABLE_HASH_TABLE_SIZE = 40
PR_TUNABLE_NEW_POOL_SIZE = 512
PR_TUNABLE_SCOREBOARD_BUFFER_SIZE = 80
PR_TUNABLE_SCOREBOARD_SCRUB_TIMER = 30
PR_TUNABLE_SELECT_TIMEOUT = 30
PR_TUNABLE_TIMEOUTIDENT = 10
PR_TUNABLE_TIMEOUTIDLE = 600
PR_TUNABLE_TIMEOUTLINGER = 30
PR_TUNABLE_TIMEOUTLOGIN = 300
PR_TUNABLE_TIMEOUTNOXFER = 300
PR_TUNABLE_TIMEOUTSTALLED = 3600
PR_TUNABLE_XFER_SCOREBOARD_UPDATES = 10

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3657

--- Comment #3 from Bernd Lommerzheim <***@lommerzheim.com> 2011-05-19 09:11:08 EDT ---
I did some investigations and found the problem. The "127.0.0.1" entry in my
"/etc/hosts" file did not directly point to "localhost":

$ cat /etc/hosts | grep '127.0.0.1'
127.0.0.1 ##running-host ##running-host2 localhost

After removing both domains in front of "localhost" the ProFTPD "api" test
suite completly passed without any failures. If this was just a
missconfiguration of my "/etc/hosts" please close this bug report. Thanks.

[b***@horde.net]

http://bugs.proftpd.org/show_bug.cgi?id=3657

TJ Saunders <***@castaglia.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |***@castaglia.org
Resolution| |WORKSFORME

--- Comment #4 from TJ Saunders <***@castaglia.org> 2011-05-19 14:13:14 EDT ---
I don't know that I'd term it a "misconfiguration" of your /etc/hosts file;
it's more that the current DNS-related API tests are brittle. There's no good
way to test DNS-related ACLs without assuming a DNS name; the only DNS name
that felt right for these sorts of unit tests was "localhost". Unfortunately,
in cases like yours, the /etc/hosts file on the test machine may not be as
expected. I'm not sure of the best solution for these cases.

I'll at least update the Test howto to mention this caveat.

Thanks for reporting the issue!