389DS memeberof plugin not working
by Ghiurea, Isabella
Hello 389 users,
I'm having problems getting the memberof plugin work on
389-Directory/1.2.11.15 B2014.219.179. We are using groupofuniquenames
groups.
Here's the configuration of the memberof plugin:
objectClass: extensibleObject (auxiliary)
objectClass: nsSlapdPlugin (structural)
objectClass: top (abstract)
cn: MemberOf Plugin
nssldap-pluginDescription: none
nssldap-pluginEnabled: on
nssldap-pluginId: none
nssldap-pluginInitfunc: memberof_postop_init
nssldap-pluginPath: libmemberof-plugin
nssldap-pluginType: postoperation
nssldap-pluginVendor: none
nssldap-pluginVersion: none
nssldap-plugin-depends-on-type: database
memberofattr: memberOf
memberofgroupattr: uniquemember
Adding members to a group do not trigger the creation of the
corresponding memberof attributes on those members. What are we missing?
Thank you,
Adrian
8 years, 6 months
- 2
- 3
Proper handling of "No original_tombstone for changenumber" errors
by Anthony Joseph Messina
Using two fully updated FreeIPA F20 masters with freeipa-
server-3.3.5-1.fc20.x86_64 and 389-ds-base-1.3.2.23-1.fc20.x86_64, I've
noticed that I'm getting a lot of the following errors in the 389 DS error
log, especially at server startup.
"No original_tombstone for changenumber=511851,cn=changelog!!"
Most often, the same changenumber repeats over and over, but there are some
other changenumbers listed as well. The changenumbers are different on each
master.
My concern is I'm preparing my thought process about the upcoming upgrade from
F20 to F21 and it looks like I may need to create a new FreeIPA master and
"migrate" the Dogtag stuff, etc. rather than a simple "yum upgrade" on each
master. Yuck!
What is the proper way to correct for these apparent errors and get these
masters working with each other in a clean manner?
Thanks. -A
--
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
8 years, 6 months
- 2
- 5