[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
libsldap: Status: 91 Mesg: openConnection: failed to connect using TLS (No such file or directory)
- To: OpenLDAP-software@OpenLDAP.org
- Subject: libsldap: Status: 91 Mesg: openConnection: failed to connect using TLS (No such file or directory)
- From: Bernd Nies <listuser@adnovum.ch>
- Date: Mon, 22 Nov 2004 09:57:06 +0100
- User-agent: Mozilla Thunderbird 0.9 (X11/20041103)
Hi,
This problem is probably not directly related with OpenLDAP but it seems
only to occur with open source software that was compiled with OpenLDAP
on Solaris which is set up as a native LDAP client.
We have Solaris 9 hosts that use LDAP as naming service. This works
fine so far. But some open source software (Postfix, Samba) compiled
with OpenLDAP does produce weird error messages like:
postfix/bounce[5730]: [ID 293258 mail.error] libsldap: Status: 91
Mesg: openConnection: failed to connect using TLS (No such file or
directory)
postfix/bounce[5730]: [ID 293258 mail.error] libsldap: Status: 7
Mesg: Session error no available conn.
smbd[26026]: [ID 293258 user.error] libsldap: Status: 91 Mesg:
openConnection: failed to connect using TLS (Bad file number)
smbd[26026]: [ID 293258 user.error] libsldap: Status: 7 Mesg: Session
error no available conn.
Doing a truss on the process id causing these errors does not show
something suspicious. Also a snoop does not show that it tries an LDAP
connection.
In the case above Postfix was compiled with OpenLDAP but it does not
use LDAP maps. Also Samba that was compiled with OpenLDAP has disabled
LDAP lookup.
Does somebody know what can cause this problem?
Thanks in advance.
Regards,
Bernd