[Date Prev][Date Next]
2.0.14 and tls bug?
- To: openldap-software@OpenLDAP.org
- Subject: 2.0.14 and tls bug?
- From: Tarjei Huse <firstname.lastname@example.org>
- Date: Sun, 16 Sep 2001 21:43:39 +0200
- User-agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.4) Gecko/20010913
I just rebuilt my deb's to include tls support, when I restart openldap,
I get the following errors:
Sep 16 21:10:02 tarjei slapd: daemon: socket() failed errno=97
(Address family not supported by protocol)
Sep 16 21:10:02 tarjei slapd: oc_check_allowed type "uniqueMember"
Sep 16 21:10:02 tarjei last message repeated 5 times
Sep 16 21:10:02 tarjei slapd: main: TLS init def ctx failed: 0
Sep 16 21:10:02 tarjei slapd: slapd shutdown: freeing system
Sep 16 21:10:03 tarjei slapd: slapd stopped.
Sep 16 21:10:03 tarjei slapd: connections_destroy: nothing to
The problem is somewhere in the libary because I cannot get pam-ldap to
work with tls either.
The setup including the cert's was working untill I upgraded to 2.0.14.
The build is the openldap2 pacakge from debian unstable where I exited
the rules file and changed --without-tls to --with-tls and removed the
Does anyone know where the misstake is? I saw something on the list
about problems relating to the FQDN but I think this should be ok for