[389-users] referential integrity postoperation plugin 1.10.12

[Picture Book]

----------------------------------------
> Date: Wed, 23 Jan 2013 10:35:38 -0700
> From: rmeggins at redhat.com
> To: picturebook16 at hotmail.com
> CC: 389-users at lists.fedoraproject.org
> Subject: Re: [389-users] referential integrity postoperation plugin 1.10.12
>
> On 01/23/2013 09:44 AM, Picture Book wrote:
> > I have this problem in a production system. So I create a test instance to confirm it. After create the test instance, I just enable the plugin without changing any configuration.
> I'm assuming you are using EL 6.3 with the EPEL6 version of 389-ds-base?
> I wonder if this bug is https://fedorahosted.org/389/ticket/410 or
> https://fedorahosted.org/389/ticket/405
>
> I haven't updated the EPEL6 389-ds-base for a while - will do so now -
> is there any chance you could try to reproduce on a "newer" platform?
Yes.I am using EL 6.3 with the EPEL6 version of 389-ds-base.
I believe that 1.2.10.12 is the latest version available on EPEL6. Really appreciate if you can update it. 

This problem doesn't exist on 1.2.11.14 on Fedora 17 that I just tried.

[23/Jan/2013:12:50:36 -0500] - 389-Directory/1.2.11.14 B2012.251.1837 starting up

> >
> > I did't change the defautl database index. It includes member, uniquemember, owner, seeAlso.
> >
> > Here's the dse.ldif
> >
> > dn: cn=referential integrity postoperation,cn=plugins,cn=config
> > objectClass: top
> > objectClass: nsSlapdPlugin
> > objectClass: extensibleObject
> > cn: referential integrity postoperation
> > nsslapd-pluginPath: libreferint-plugin
> > nsslapd-pluginInitfunc: referint_postop_init
> > nsslapd-pluginType: postoperation
> > nsslapd-pluginEnabled: on
> > nsslapd-pluginprecedence: 40
> > nsslapd-pluginarg0: 0
> > nsslapd-pluginarg1: /var/log/dirsrv/slapd-test/referint
> > nsslapd-pluginarg2: 0
> > nsslapd-pluginarg3: member
> > nsslapd-pluginarg4: uniquemember
> > nsslapd-pluginarg5: owner
> > nsslapd-pluginarg6: seeAlso
> > nsslapd-plugin-depends-on-type: database
> > nsslapd-pluginId: referint
> > nsslapd-pluginVersion: 1.2.10.12
> > nsslapd-pluginVendor: 389 Project
> > nsslapd-pluginDescription: referential integrity plugin
> > modifiersName: uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoo
> >
> > ----------------------------------------
> >> Date: Wed, 23 Jan 2013 09:35:41 -0700
> >> From: rmeggins at redhat.com
> >> To: 389-users at lists.fedoraproject.org
> >> CC: picturebook16 at hotmail.com
> >> Subject: Re: [389-users] referential integrity postoperation plugin 1.10.12
> >>
> >> On 01/23/2013 09:22 AM, Picture Book wrote:
> >>> After enabling the refertial integrity postoperation plugin, I created a user and a group with the user as member. When I changed the user's rdn: uid. I got the following error, and the uniquememeber of the group didn't change.
> >>>
> >>> Is this a known problem?
> >> No.
> >>
> >>> [23/Jan/2013:11:01:34 -0500] - 389-Directory/1.2.10.12 B2012.180.1623 starting up
> >>> [23/Jan/2013:11:01:34 -0500] - slapd started. Listening on All Interfaces port 6389 for LDAP requests
> >>> [23/Jan/2013:11:03:08 -0500] - slapi_modify_internal_set_pb: NULL parameter
> >>> [23/Jan/2013:11:03:08 -0500] - allow_operation: component identity is NULL
> >> Can you provide your referint plugin configuration?
> >>
> >>> --
> >>> 389 users mailing list
> >>> 389-users at lists.fedoraproject.org
> >>> https://admin.fedoraproject.org/mailman/listinfo/389-users
> >>
>