I am hitting an issue with reinitializing the directory database.
Basically I have two directory servers and they're configured using multi-master replication scheme.
When I reinitialize the directory database, the directory became inaccessible. I think it is related with my multi-master replication setup because when I use only reinitialize one LDAP, it would work just fine
My question is if multi-master replication is enabled on two LDAPs then do I need to reinitialize both LDAPs at the same time or just one LDAP?
Thanks!
- David
On Fri, May 14, 2010 at 4:42 PM, Chun Tat David Chu <beyonddc.storage@xxxxxxxxx> wrote:
Reinitializing the directory database does the trick! I'm going to do more testing on it.
Thanks a lot!
- DavidOn Fri, May 14, 2010 at 1:43 PM, David Boreham <david_list@xxxxxxxxxxx> wrote:
Yes. Import an almost empty LDIF file. You can also copy the on-diskOn 5/14/2010 11:40 AM, Chun Tat David Chu wrote:
>
> We use 389 Directory as part of our development lab. Every time when
> we do a new test, we need to repopulate our 389 directory to a clean
> slate (i.e. delete all existing data and re-create a base hierarchy
> tree).
>
> Our current way of doing so is simply using the ldapdelete command to
> remove all existing data and use ldapadd to re-create the base
> hierarchy tree. This approach is okay but sometime it could take up
> to 20 to 30 minutes to delete all existing data depending on the
> amount of data saved in the directory.
>
> Is there a more efficient way to repopulate the 389 Directory?
database underneath a server (when it is shut down), if you know what
you're doing.
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
