[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Problems After Upgrade
- To: OpenLDAP-software@OpenLDAP.org
- Subject: Problems After Upgrade
- From: David Wheeler <justatheory@gmail.com>
- Date: Thu, 29 Sep 2005 13:01:38 -0700
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=lKVbI0dDYXIo8mWQ6K7hwnMoet+nojTFf3tjevckMuhaCBq5CHmcr3oUydCtZkiOQvnu5RZ2QysSscP0fQQ9V+Ur0mIJ4UVcRnM1BdKsxr0CTago8s0zlL8eSuB6UY7FQvszDp7sOjH2QkogA8Xf8E4axf2WQeywSisyl097tkU=
I installed 2.3.7 over 2.2.26 and can no longer connect to the
OpenLDAP server. This is what I'm seeing in my error log:
Sep 29 12:38:42 sahlins
root@sahlins.kineticode.com:/usr/local/src/openldap-2.3.7/servers/slapd
Sep 29 12:38:42 sahlins Expect poor performance for suffix dc=kineticode,dc=com.
Sep 29 12:59:25 sahlins authdaemond.ldap: ldap_simple_bind_s failed:
Internal (implementation specific) error
Is there perhaps some configuration setting that I need to tweak to
get this to work? Or maybe a document that explains what I'd need to
adjust when jumping to the new version?
Many TIA,
David