Yup. that did the trick. I never modified the file but I did inherit this project/configuration. The timestamps on the files are the same, so I am not sure what happened here. THANK YOU SO MUCH for the help on fixing this problem! /mrg On Mar 2, 2012, at 13:32, Nathan Kinder wrote: > On 03/02/2012 06:32 AM, Michael R. Gettes wrote: >> On Mar 2, 2012, at 9:21, Rich Megginson wrote: >> >>> On 03/01/2012 09:56 PM, Michael R. Gettes wrote: >>>> I am in process of standing up a new directory service and will have to migrate many apps to the new service. Do you believe 1.2.10.2 is stable enough for production use? I would trust your assessment. I realize the caveats of any recommendation you might make. >>> It's hard to say - we have people using 1.2.10.2 in production on EL6 and Fedora - but none on EL5 that I'm aware of. >>> >>> So, best to stick with 1.2.9.9 for production until we get some more feedback on 1.2.10.2 >> let me see how i can try it out… not sure given how we maintain things. >> >>> That being said, I was hoping you could try it out and see if it still has the problem. >>> >>> Perhaps it is a schema problem? >>> >>> grep -i changenumber /etc/dirsrv/slapd-INST/schema/* >>> grep -i entryusn /etc/dirsrv/slapd-INST/schema/* >> on 1.2.9.9 >> >> #grep -i changenumber * >> 02common.ldif:attributeTypes: ( 2.16.840.1.113730.3.1.5 NAME 'changeNumber' DESC 'Changelog attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 X-ORIGIN 'Changelog Internet Draft' ) >> 02common.ldif:objectClasses: ( 2.16.840.1.113730.3.2.1 NAME 'changeLogEntry' DESC 'LDAP changelog objectclass' SUP top MUST ( targetdn $ changeTime $ changenumber $ changeType ) MAY ( changes $ newrdn $ deleteoldrdn $ newsuperior ) X-ORIGIN 'Changelog Internet Draft' ) >> # grep -i entryusn * >> 01core389.ldif.rpmnew:attributeTypes: ( 2.16.840.1.113730.3.1.2096 NAME 'entryusn' DESC 'Netscape defined attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 SINGLE-VALUE NO-USER-MODIFICATION USAGE directoryOperation X-ORIGIN 'Netscape' ) > The problem here seems to be that it is a *.rpmnew file. This is causing your schema to not be updated from the upgrade. Did you customize your 01core389.ldif file at some point? > > Do a diff between 01core389.ldif and 01core389.ldif.rpmnew. >> >> on 1.2.8.3 >> >> # grep -i changenumber * >> 02common.ldif:attributeTypes: ( 2.16.840.1.113730.3.1.5 NAME 'changeNumber' DESC 'Changelog attribute type' SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 X-ORIGIN 'Changelog Internet Draft' ) >> 02common.ldif:objectClasses: ( 2.16.840.1.113730.3.2.1 NAME 'changeLogEntry' DESC 'LDAP changelog objectclass' SUP top MUST ( targetdn $ changeTime $ changenumber $ changeType ) MAY ( changes $ newrdn $ deleteoldrdn $ newsuperior ) X-ORIGIN 'Changelog Internet Draft' ) >> # grep -i entryusn * >> # >> >> yep, that's nothing on entryusn >> >> /mrg >> >>>> Thanks! >>>> >>>> /mrg >>>> >>>> On Mar 1, 2012, at 23:16, Rich Megginson wrote: >>>> >>>>> This code has changed with 389-ds-base 1.2.10.2 - any chance you could try that version, in epel-testing? >>>>> >>>> -- >>>> 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 > > -- > 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
