Re: [389-users] Directory Re-population

2010-06-23 Thread Rich Megginson
Chun Tat David Chu wrote: Hi Rich, Thanks for helping. I followed your direction and exported another LDIF for my 2nd database but whenever I try to load it I get an error message ldap_add: Operations error. What's in the errors log? Here's a little information on my DIT hierarchy.

Re: [389-users] Directory Re-population

2010-06-23 Thread Chun Tat David Chu
Hi Rich, I looked at both access log and error log. The access log has an addition of ldap_add failure but the error log doesn't say anything about the failure on loading the 2nd database. - David Access Log [23/Jun/2010:18:37:09 -0400] conn=12180 fd=118 slot=118 connection from 138.125.205.65

Re: [389-users] Directory Re-population

2010-06-23 Thread Rich Megginson
Chun Tat David Chu wrote: Hi Rich, I looked at both access log and error log. The access log has an addition of ldap_add failure but the error log doesn't say anything about the failure on loading the 2nd database. What were the exact command line arguments you passed to ldif2db.pl? It

Re: [389-users] Directory Re-population

2010-06-23 Thread Chun Tat David Chu
Hi Rich, d'oh! My bad... You're absolutely correct! It is now working properly. Thanks! - David On Wed, Jun 23, 2010 at 6:48 PM, Rich Megginson rmegg...@redhat.com wrote: Chun Tat David Chu wrote: Hi Rich, I looked at both access log and error log. The access log has an addition

Re: [389-users] Directory Re-population

2010-06-22 Thread Rich Megginson
Chun Tat David Chu wrote: Another question about directory re-population. If I want to create a generic LDIF backup for a bunch of test directory servers, in the exported LDIF file, should I remove the following attributes? or it doesn't really matter? nsUniqueId:

Re: [389-users] Directory Re-population

2010-06-22 Thread Chun Tat David Chu
Hi Rich, I did some testing and it appears to be working as you expected. The steps involve 1) Export the directory database to a LDIF 2) Reload the directory database 3) Reinitialize the consumer I have another question. I noticed there's an ACI on the directory database LDIF. aci: (targetattr

Re: [389-users] Directory Re-population

2010-06-22 Thread Rich Megginson
Chun Tat David Chu wrote: Hi Rich, I did some testing and it appears to be working as you expected. The steps involve 1) Export the directory database to a LDIF 2) Reload the directory database 3) Reinitialize the consumer I have another question. I noticed there's an ACI on the

Re: [389-users] Directory Re-population

2010-06-22 Thread Chun Tat David Chu
Thanks Rich, I did more experiment, and I noticed one of my database didn't get reload after I ran ldif2db.pl script My DIT has a root database and then a sub database under the root database. When I did the export, I exported from the root database. When I ran the ldif2db.pl script, only the

Re: [389-users] Directory Re-population

2010-06-22 Thread Rich Megginson
Chun Tat David Chu wrote: Thanks Rich, I did more experiment, and I noticed one of my database didn't get reload after I ran ldif2db.pl http://ldif2db.pl script My DIT has a root database and then a sub database under the root database. When I did the export, I exported from the root

Re: [389-users] Directory Re-population

2010-06-18 Thread Chun Tat David Chu
Thanks Rich, I'll give that a try. On Fri, Jun 18, 2010 at 4:20 PM, Rich Megginson rmegg...@redhat.com wrote: Chun Tat David Chu wrote: Hi Rich, Thanks for replying. Just making sure I'm using the right utility. To reinitialize the directory, I use the ldif2db.pl http://ldif2db.pl

Re: [389-users] Directory Re-population

2010-06-18 Thread Chun Tat David Chu
Hi all, 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

Re: [389-users] Directory Re-population

2010-06-18 Thread Rich Megginson
Chun Tat David Chu wrote: Hi all, 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

Re: [389-users] Directory Re-population

2010-06-18 Thread Chun Tat David Chu
Hi Rich, Thanks for replying. Just making sure I'm using the right utility. To reinitialize the directory, I use the ldif2db.pl Perl script right? - David On Fri, Jun 18, 2010 at 3:58 PM, Rich Megginson rmegg...@redhat.com wrote: Chun Tat David Chu wrote: Hi all, I am hitting an issue

Re: [389-users] Directory Re-population

2010-06-18 Thread Rich Megginson
Chun Tat David Chu wrote: Hi Rich, Thanks for replying. Just making sure I'm using the right utility. To reinitialize the directory, I use the ldif2db.pl http://ldif2db.pl Perl script right? Yes, if you need to restore _all_ servers from an LDIF backup. The reason I say _all_ is that

[389-users] Directory Re-population

2010-05-14 Thread Chun Tat David Chu
Hi All, 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

Re: [389-users] Directory Re-population

2010-05-14 Thread David Boreham
On 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

Re: [389-users] Directory Re-population

2010-05-14 Thread Chun Tat David Chu
Reinitializing the directory database does the trick! I'm going to do more testing on it. Thanks a lot! - David On Fri, May 14, 2010 at 1:43 PM, David Boreham david_l...@boreham.orgwrote: On 5/14/2010 11:40 AM, Chun Tat David Chu wrote: We use 389 Directory as part of our development