Date: Thu, 29 Jul 2004 11:01:12 -0500 From: Kirk Strauser <kirk@strauser.com> To: freebsd-current@freebsd.org Subject: Upgrading to net/openldap22-sasl-server giving fits Message-ID: <200407291101.15091.kirk@strauser.com>
next in thread | raw e-mail | index | archive | help
--Boundary-02=_L9RCBut877YPYN4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline My 5.2-CURRENT server is happily chugging away using openldap21-sasl-server= =20 with the db41 backend, nss_ldap, and pam_ldap for user authentication. =20 After reading in /usr/ports/UPDATING that openldap22-(sasl-)?server was=20 becoming the default I thought I'd try upgrading to it. Unfortunately, upgrading to openldap22 with db41 results in: bdb_initialize: initialize BDB backend bdb_initialize: Sleepycat Software: Berkeley DB 4.1.25: (December 19, 2002) >>> dnNormalize: <cn=3DSubschema> =3D> ldap_bv2dn(cn=3DSubschema,0) <=3D ldap_bv2dn(cn=3DSubschema,0)=3D0 =3D> ldap_dn2bv(272) <=3D ldap_dn2bv(cn=3Dsubschema,272)=3D0 <<< dnNormalize: <cn=3Dsubschema> >>> dnNormalize: <> <<< dnNormalize: <> Unrecognized database type (bdb) database bdb initialization failed. slapd shutdown: freeing system resources. slapd stopped. connections_destroy: nothing to destroy. =2E..and upgrading from db41 to db42 results in an unreadable database. Ha= s=20 anyone successfully moved from OpenLDAP 2.1 to 2.2?=20 =2D-=20 Kirk Strauser --Boundary-02=_L9RCBut877YPYN4 Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- iD8DBQBBCR9L5sRg+Y0CpvERAofJAKCCnZds4dwYGH4UMY03QNjfb+E8cgCfdWOo JNebL4VpHtFMzqeIr1Faej8= =/njh -----END PGP SIGNATURE----- --Boundary-02=_L9RCBut877YPYN4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407291101.15091.kirk>