Re: Recover directory database files when disk fills up!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Howard Wilkinson wrote:
Rich Megginson wrote:
Howard Wilkinson wrote:
Richard Megginson wrote:
Howard Wilkinson wrote:

These are messages from sasl. I believe you can ignore them, I don't think they have anything to do with the problem.


What can I do to recover the database so that I can start the server?
What messages do you get in the directory server error log?

        Fedora-Directory/1.1.1 B2008.151.1915
        bastion.finsbury.cohtech.co.uk:636 (/etc/dirsrv/slapd-bastion)

    [04/Aug/2008:10:40:15 +0100] - Fedora-Directory/1.1.1
    B2008.151.1915 starting up
    [04/Aug/2008:10:40:15 +0100] - Detected Disorderly Shutdown last
    time Directory Server was running, recovering database.
    [04/Aug/2008:10:40:17 +0100] - libdb: file userRoot/id2entry.db4
    has LSN 518/7178886, past end of log at 1/4431
    [04/Aug/2008:10:40:17 +0100] - libdb: Commonly caused by moving a
    database from one database environment
    [04/Aug/2008:10:40:17 +0100] - libdb: to another without clearing
    the database LSNs, or by removing all of
    [04/Aug/2008:10:40:17 +0100] - libdb: the log files from a
    database environment

How did you create the backup?

[Snip]

There was no backup created. The system ran out of disk space in the log partition and in the database partition during an OS upgrade. It looks ike the version of db4 has changed and the directory server failed while this was happening. I would like to recover by rolling forward if possible, but if not this is a multi-master instance and I can probably rebuild if I have to.
Ok, I see. I'm not sure if directory server auto-recovery is possible with this sort of failure. You might be able to use the berkeley db command line utilities to upgrade and/or recover your database files. http://www.oracle.com/technology/documentation/berkeley-db/db/utility/index.html - you may have to figure out which version of bdb you are using, then find the appropriate documentation - rpm -qi db4 or rpm -qi db4-utils. You might try db2ldif to export your data, then re-import using ldif2db, but that would force a replication re-init anyway.

Howard.

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

<<attachment: smime.p7s>>

--
Fedora-directory-users mailing list
Fedora-directory-users@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-directory-users

[Index of Archives]     [Fedora Directory Users]     [Fedora Directory Devel]     [Fedora Announce]     [Fedora Legacy Announce]     [Kernel]     [Fedora Legacy]     [Share Photos]     [Fedora Desktop]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Big List of Linux Books]     [Gimp]     [Yosemite News]

  Powered by Linux