[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Upgrade to 2.3.40 -> failed index

Quanah Gibson-Mount wrote:

--On February 4, 2008 7:22:09 PM -0800 "Paul B. Henson"<henson@acm.org> wrote:

On Mon, 4 Feb 2008, Quanah Gibson-Mount wrote:

slapadd always creates at least one log file that would not be removed by
automatic removal.  If you had no log files when you were done, then
something was done wrong.
There's not much to slapadd, I'm not sure what could have been done
wrong... I did use the -q option (otherwise it takes untractably long),
but there were no errors or interruptions and the database created worked
fine for 10 months or so.

So you can see here -- Slapadd completes.  Now, it only creates a partial
BDB environment (That's why there are two __db.* files).  After it
completes, before you can copy it anywhere, you need to run db_recover to
clean that environment out, which I noted quite a long time ago.

No. slapd will do the necessary recovery automatically in this case.

Paul's right - assuming the slapadd went well and nothing else was done, then a binary copy of the DB directory should have worked fine on another machine.

Still the fact remains that simply upgrading the slapd version from 2.3.35 to 2.3.40 wouldn't have done anything to the transaction log files, and the only reason that BDB would complain about those missing Log Sequence Numbers is because the log files no longer matched the database files.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/