[EMAIL PROTECTED] writes: > Hi all, > > Our clients live server (Redhat) experienced some problems this > morning, and as a result they had to restart it. But apparently ldap > wasn't able to do everything it wanted before it got killed, because > during bootup it said: > > Checking configuration files for : bdb_db_open: unclean shutdown > detected; attem > pting recovery. > bdb_db_open: Recovery skipped in read-only mode. Run manual recovery > if errors a > re encountered.
I presume you are referring to OpenLDAP. [...] > 4. The main problem seems to have been that ldap wasn't able to write > all its file changes before it got killed during the shutdown/reboot. > What can I do to make this less likely to happen (or stop it from > happening completely)? I read somewere about "committing the logs more > frequently", but how? >From OpenLDAP-2.4.6 man slapd-bdb(5), checkpoint <kbyte> <min> Specify the frequency for checkpointing the database transaction og. A checkpoint operation flushes the database buffers to disk and writes a checkpoint record in the log. In addition consider the BerkeleyDB flag db_log_autoremove -Dieter -- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6 --- You are currently subscribed to [EMAIL PROTECTED] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.