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

Re: BDB database not synced to file

Aaron and Buchan thank you both for your quick response, and
please accept my apologize for late answer. I have so much
work that I've simply unable to answer before (ok. maybe not
exactly unable :)

ad Aaron's mail
I've upgraded my debian server and now slapd is of version 2.2.23
and it seems to work just fine. To put some shame of me I have to
say that putting the question on this list was my last resort
since I have googled for days, read the manuals and I even put
the option "checkpoint 1 10" into my slapd.conf, but it didn't help.

After I while I forgot that I should upgrade slapd, and I began to
think I'm doing something terribly wrong, so I had to ask. To avoid
any confusion I said "There is no bdb options in slapd.conf". So
I lied a bit, but in good will.

ad Buchan's mail
There is automatic recovery of the slapd database in debian
start up script but not for the version of slapd I've had installed.
Now it is working OK.

Again, thank you very much to both of you.

Best regards,
   Damir Koscic

----- Original Message ----- From: "Aaron Richton" <richton@nbcs.rutgers.edu>
To: "Damir Koscic" <Damir.Koscic@ladon.hr>
Cc: "OpenLDAP-software" <OpenLDAP-software@OpenLDAP.org>
Sent: Thursday, September 15, 2005 2:40 PM
Subject: Re: BDB database not synced to file

Well, to get to your immediate concern, if you have no bdb options, then
the bdb "checkpoint" directive defaults to "checkpoint 0 0", which would
result in no checkpoints, which could result in "not synced to file" (as
you put it).

So, to start, you want to look through slapd-bdb(5) man page, Berkeley DB
documentation to understand/make a DB_CONFIG file, mailing list archives
and the OpenLDAP FAQ-O-Matic for guidelines/suggestions as to how to
calculate some sane values for these, etc.

On top of that, version 2.1.30 is historic. It would not be surprising if
there are bugs in there that nobody even knows about. You would be well
advised to undertake an upgrade to 2.3.7, again making sure to read the
slapd-bdb(5) (or whatever backend you choose to use) man page and
configure properly with the appropriate directives for that version. Any
perceived ease-of-use you may have from using a vendor supplied version, I
would argue, is more than outstripped by the possible downtime that bugs
in an old version may incur (e.g. to your Samba domain, in your case).

Finally, if your slapd has an unclean shutdown, in versions earlier than
2.3 you must run the "db_recover" command from Sleepycat to recover your
database, PRIOR to slapd startup. In version 2.3, this is done
automatically; yet another incentive to upgrade.