Re: [389-users] Repair replication

Hey Herb, You should refer to the Red Hat Directory Server administration guide for detail about setting up replication which you can locate in here. http://docs.redhat.com/docs/en-US/Red_Hat_Directory_Server/ >> 1. How can I find out which system(s) is/are master, consumer, hub, etc? You should

Re: [389-users] LDAPS configuration/installation

The cheat sheet is here http://directory.fedoraproject.org/wiki/Howto:SSL You just need to read it first and then give it a try. I followed this instruction couple years ago. - dc 2012/3/5 Arpit Tolani > Hie > > 2012/3/5 Gilbert Martin > >> Hi All, >> >> I've been trying to get SSL working w

Re: [389-users] attrcrypt_unwrap_key: failed to unwrap key for cipher AES

Hi Rich, Can you tell me what triggers this message? Thanks, David 2010/12/17 Rich Megginson > On 12/16/2010 03:41 PM, Chun Tat David Chu wrote: > > Hi All, > > Occasionally I see the following messages when I start the 389DS. > > attrcrypt_unwrap_key: failed to unwr

[389-users] ldap_add: Already exists (68)

Hi All, After upgrading 389 Directory Server, I am getting a "ldap_add: Already exists (68)" error message when importing a used to be working LDIF via the ldapmodify command. Can someone help me to confirm that they are seeing the same thing? Adding the entry itself is fine but the problem occu

[389-users] NSMMReplicationPlugin - Can't resurrect tombstone

Hi all, I am hitting some problem with my replicated directory server. I saw the following error messages from the errors log file. [17/Sep/2010:09:47:51 -0400] NSMMReplicationPlugin - conn=1 op=4 csn=4c9363a90002: Can't resurrect tombstone ou=test,dc=example,dc=com to glue reason 'delet

Re: [389-users] ns-slapd processes not dying

Hi, We had similar problem before, but I am not sure if it is related to your case. The file descriptors that were opened by the ns-slapd process was all in a CLOSE_WAIT state. You can try execute "netstat -anput | grep CLOSE_WAIT" and see if there's a lot of dangling CLOSE_WAIT socket opened by

Re: [389-users] Directory Re-population

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 wrote: > Chun Tat David Chu wrote: > > Hi Rich, > > > > I looked at both access log and error log. The ac

Re: [389-users] Directory Re-population

Processed 97 entries (91 entries were skipped because they don't belong to this database) in 1 seconds. (97.00 entries/sec) On Wed, Jun 23, 2010 at 6:34 PM, Rich Megginson wrote: > Chun Tat David Chu wrote: > > Hi Rich, > > > > Thanks for helping. I followed your direc

Re: [389-users] Directory Re-population

y the root database get reloaded but not the sub database. Do you have any ideas? Thanks in advance - David On Tue, Jun 22, 2010 at 5:30 PM, Rich Megginson wrote: > Chun Tat David Chu wrote: > > Hi Rich, > > > > I did some testing and it appears to be working as you expec

Re: [389-users] Directory Re-population

irectory database into another LDAP? Essentially I want to use a basic directory database LDIF and load it to a bunch of different development LDAP we have. Some LDAPs are multi-mastered configured and most are not. Thanks in advance - David On Tue, Jun 22, 2010 at 2:43 PM, Rich Megginson wrote: >

Re: [389-users] Directory Re-population

sName: modifiersName: cn=directory manager createTimestamp: 20100514213428Z modifyTimestamp: 20100514213430Z My LDIF backup will be imported back to the LDAP using ldif2db.pl. - David On Fri, Jun 18, 2010 at 4:40 PM, Chun Tat David Chu < beyonddc.stor...@gmail.com> wrote: > Thanks Rich, I'

Re: [389-users] Directory Re-population

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 wrote: > Chun Tat David Chu wrote: > > Hi all, > > > >

Re: [389-users] Directory Re-population

n Tat David Chu < beyonddc.stor...@gmail.com> wrote: > 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 wrote: > >> On 5/14/2

Re: [389-users] Directory Re-population

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 wrote: > On 5/14/2010 11:40 AM, Chun Tat David Chu wrote: > > > > We use 389 Directory as part of our developm

[389-users] Directory Re-population

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 remov

[389-users] Quick question about RHDS

Not sure if this is a good place to ask. I was just wondering what is how often a new version of RHDS is release? The latest RHDS is 8.1, is there an estimation of when RHDS 8.2 would be release? Thanks, David -- 389 users mailing list 389-us...@lists.fedoraproject.org https://admin.fedoraproject

[389-users] Referral and Read-Only Replica Consumer

Hi All, I have an issue on referral and read-only replica. My setup consists of two multi-master suppliers and 1 read-only replica consumer. MM1 <-> MM2 | | | | >C<- The replication is configured to use SSL, port 636. I notice that the automatic referral

Re: [389-users] slapd didn't close connection and get into CLOSE_WAIT state

Thank you Rich, I will definitely help testing the alpha release once it is available. On Thu, Mar 11, 2010 at 9:24 AM, Rich Megginson wrote: > Chun Tat David Chu wrote: > > Hi Rich, > > > > Thanks for your explanation. > > > > I know that #567429 is a low

[389-users] slapd didn't close connection and get into CLOSE_WAIT state

Hi All, I am running 389 DS version 1.2.5, build number 2010.012.2034 on RHEL 5.2. I have a problem that slapd didn't close a connection and eventually get into a CLOSE_WAIT state after my JAVA application exit. The scenario only happen when my application registers a NamingListener via the JAVA

[389-users] yum repository and 389 Directory Server 1.2.5

Hi All, I have a quick question. I am using Fedora 12 and just installed 389 Directory Server yesterday. I followed the instruction on the yum installation guide, http://directory.fedoraproject.org/wiki/Install_Guide. - yum install 389-ds I am not sure why it installed 389 DS 1.2.3 instead of 1

Re: [389-users] [389-devel] Fatal Error: Could not create directory server instance

Marc Sauton > Marc Sauton wrote: > >> Chun Tat David Chu wrote: >> >>> Hi Rich, >>> >>> My apology, I'm actually using Red Hat DS. I knew that I would get a >>> much faster response on the 389 mailing list. ;) >>> >>> Fr