When attribute values are deleted from entries in a replicated partition they are moved to a hidden state, they need to be kept around in case they need to be resurrected by the update resolution protocol. If you add the same value after deleting it, the underlying mechanism moves it back from the hidden state. I wonder if it's considering the old value equivalent to what you're trying to add. I'm pretty sure spaces don't slip through though, can you verify what character codes the trailing characters are so I can test it? Ulf Eddie C wrote: > I have tried adding/removing these attributes a number of different > ways. LDIF/LDAP Browser/ FDS admin console. I fully remove the values > and the entire attribute but when I re-add them they keep having extra > spaces in the end. I almost believe the entry is corrupted in some > way. > > I do not want to do anything very drastic because only this one entry > is showing problems (that I know of) > > > > On 9/24/07, Dan Lannom <dlannom at umd.umich.edu> wrote: > >> Eddie C wrote: >> >>> I am having an issue that may be related to multi-master replication, >>> or it may be related to a non viewable ascii value in an attribute. >>> >>> We have a custom schema. We have a multivalued attribute >>> departalloweddomain >>> >>> this attribute has three values inside it. >>> "a.com" >>> "b.com " >>> "c.com " >>> >>> My goal is to remove the trailing white space. Which may be a space or >>> a weird character. >>> >> You can determine what the white space is by saving an .ldif >> representation [ldapsearch -LLL ... > file]and viewing with a program >> that views hexcodes like xxd. >> >> >> >>> I have tried deleting the individual values and re-adding them. >>> I attempted to delete the entire attribute and re-add. >>> >>> The value keeps appearing like so. >>> >>> "b.com " >>> >>> >> Try editing the .ldif file above and removing the extra characters, >> modify enough of the attributes so that its unique and add it into the >> directory using ldapmodify or other standard tool. If this still shows >> a problem then there is something very unusual about your configuration. >> If importing the .ldif file is clean I would suspect the technique >> used to normally add the attributes. >> >> Dan Lannom >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20070925/19544cd3/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 6097 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20070925/19544cd3/attachment.bin
