(Answer) (Category) OpenLDAP Faq-O-Matic : (Category) OpenLDAP Software FAQ : (Category) Common Errors : (Answer) `make test' fails
Some times, `make test' fails at the very first test with an obscure message like
    make test
    make[1]: Entering directory `/ldap_files/openldap-2.2.13/tests'
    make[2]: Entering directory `/ldap_files/openldap-2.2.13/tests'
    Initiating LDAP tests for BDB...
    Cleaning up test run directory leftover from previous run.
    Running ./scripts/all...
    >>>>> Executing all LDAP tests for bdb
    >>>>> Starting test000-rootdse ...
    running defines.sh
    Starting slapd on TCP/IP port 9011...
    Using ldapsearch to retrieve the root DSE...
    Waiting 5 seconds for slapd to start...
    ./scripts/test000-rootdse: line 40: 10607 Segmentation fault $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING >$LOG1 2>&1
    Waiting 5 seconds for slapd to start...
    Waiting 5 seconds for slapd to start...
    Waiting 5 seconds for slapd to start...
    Waiting 5 seconds for slapd to start...
    Waiting 5 seconds for slapd to start...
    ./scripts/test000-rootdse: kill: (10607) - No such pid
    ldap_bind: Can't contact LDAP server (-1)
    >>>>> Test failed
    >>>>> ./scripts/test000-rootdse failed (exit 1)
    make[2]: *** [bdb-yes] Error 1
    make[2]: Leaving directory `/ldap_files/openldap-2.2.13/tests'
    make[1]: *** [test] Error 2
    make[1]: Leaving directory `/ldap_files/openldap-2.2.13/tests'
    make: *** [test] Error 2
or so. Usually, the five lines
    Waiting 5 seconds for slapd to start...
indicate that slapd didn't start at all.

For OpenLDAP 2.2 and later, in tests/testrun/slapd.1.log there is a full log of what slapd wrote while trying to start. The log level can be increased by setting the environment variable SLAPD_DEBUG to the corresponding value; see loglevel in slapd.conf(5) for the meaning of log levels.

A typical reason for this behavior is a runtime link problem, i.e. slapd cannot find some dynamic libraries it was linked against. Try running ldd(1) on slapd (for those architectures that support runtime linking).

There might well be other reasons; the contents of the log file should help clarifying them.

Tests that fire up multiple instances of slapd typically log to tests/testrun/slapd.<n>.log, with a distinct <n> for each instance of slapd; list tests/testrun/ for possible values of <n>.

[Append to This Answer]
Previous: (Answer) ldap_read: want=# error=Resource temporarily unavailable
Next: (Answer) ldap_*: Internal (implementation specific) error (80) - additional info: entry index delete failed
This document is: http://www.openldap.org/faq/index.cgi?file=1089
[Search] [Appearance]
This is a Faq-O-Matic 2.721.test.
© Copyright 1998-2013, OpenLDAP Foundation, info@OpenLDAP.org