Date: Thu, 29 Jul 2004 11:21:41 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-current@freebsd.org Subject: Re: Upgrading to net/openldap22-sasl-server giving fits Message-ID: <20040729111516.U63843@carver.gumbysoft.com> In-Reply-To: <200407291101.15091.kirk@strauser.com> References: <200407291101.15091.kirk@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jul 2004, Kirk Strauser wrote: > My 5.2-CURRENT server is happily chugging away using openldap21-sasl-server > with the db41 backend, nss_ldap, and pam_ldap for user authentication. > After reading in /usr/ports/UPDATING that openldap22-(sasl-)?server was > becoming the default I thought I'd try upgrading to it. > > Unfortunately, upgrading to openldap22 with db41 results in: [...] It would not suprise me if you need to dump + reload your database to update to a new bdb schema in openldap2.2. Did you try backing up the old db files, slapcatting them somewhere, move out of the way, do the upgrade, then slapadd the data back into fresh db files? Actually there's a mention of this in their FAQ-O-Matic: http://www.openldap.org/faq/data/cache/842.html Dump + reload on upgrade are well known to postgres folks :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040729111516.U63843>