Since it appears that you're using BerkeleyDB 4.5 which is not the default version installed on your platform, most likely you have conflicting libdb libraries loaded. If you're using the default libsasl2, then this is certainly the problem. You can find out for sure by running slapd under gdb. When it crashes use the command "info shared" to see what shared libraries are present. If you see two different versions of libdb, that's your problem. You'll need to rebuild whatever other libraries are using the other libdb version and get everything onto the same version.
At any rate, I don't believe there's any bug in OpenLDAP software here. This ITS will be closed.
saint.cn@gmail.com wrote:
Full_Name: Jack Chen Version: 2.3.27 OS: Redhat AS 3.0 2.4.21-40.ELsmp URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (60.12.9.18)
I found when I run ldap commands without arguments always get password imput requirement before result. But the command always told me "ldap_sasl_interactive_bind_s: Can't contact LDAP server". Then I found the slapd crashed.
Then I start slpad with command like "slpad -d 256" with root account and want to get debug information before slpad crash.
Then following is the startup information:
@(#) $OpenLDAP: slapd 2.3.27 (Sep 30 2006 16:10:17) $ root@caivs:/home/jack/tools/openldap-2.3.27/servers/slapd daemon: IPv6 socket() failed errno=97 (Address family not supported by protocol) bdb_db_open: unclean shutdown detected; attempting recovery. bdb_db_open: Warning - No DB_CONFIG file found in directory /usr/local/openldap/var/openldap-data: (2) Expect poor performance for suffix dc=test,dc=com. slapd starting =====================================================================
And when I input command "ldapsearch" in shell with root account, and input password with any words and return. The command tell me like following: ===================================================================== /usr/local/BerkeleyDB.4.5/bin:$ldapsearch SASL/DIGEST-MD5 authentication started Please enter your password: ldap_sasl_interactive_bind_s: Can't contact LDAP server =====================================================================
And I check the console which is running slapd, and get following information:
conn=0 fd=10 ACCEPT from IP=127.0.0.1:33518 (IP=0.0.0.0:389) conn=0 op=0 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" conn=0 op=0 SRCH attr=supportedSASLMechanisms conn=0 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text= conn=0 op=1 BIND dn="" method=163 conn=0 op=1 RESULT tag=97 err=14 text= conn=0 op=2 BIND dn="" method=163 /etc/sasldb2: Successful return: 0 segment fault (core dumped) =====================================================================