I went through and re-init both of the databases on the problem machine, but still get the same errors. Also, if I restart FDS on the box, it claims to have been shutdown in a disorderly manner, even when I use stop-slapd. There are no errors related to the shutdown. It sounds like the BDB backend is pretty hosed, and even the auto recovery isn't completely handling it. Ideas? Chris St. Pierre Unix Systems Administrator Nebraska Wesleyan University On Thu, 5 Oct 2006, Richard Megginson wrote: > Chris St. Pierre wrote: >> On Thu, 5 Oct 2006, Richard Megginson wrote: >> >> >> > Do you have another master? If so, just perform a replica initialization >> > (using the console). >> > >> >> We've got three other masters, but we don't use the console -- or have >> X installed or heads on the machines. Can this be done from the CLI, >> maybe with mmr.pl? >> > Not sure about mmr.pl, but yes, this can be done via ldapmodify. > First, you have to find the DN of the replication agreement from another master > to the one you want to initialize. > ldapsearch -x -h othermaster -D "cn=directory manager" -w password -s sub -b > cn=config "objectclass=nsDS5ReplicationAgreement" cn nsDS5ReplicaHost > nsDS5ReplicaPort > There may be several, you'll have to figure out which one goes to the master > you want to initialize > > Next, use ldapmodify to start the repl init: > ldapmodify -x -h othermaster -D "cn=directory manager" -w password > dn: dn of the repl agreement > changetype: modify > replace: nsds5BeginReplicaRefresh > nsds5BeginReplicaRefresh: start > > Then check the error logs for both masters to see when repl init is completed. >> Chris St. Pierre >> Unix Systems Administrator >> Nebraska Wesleyan University >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >
