Hi,
On Dec 3, 2018, at 6:59 PM, Florence Blanc-Renaud flo@redhat.com wrote: I already saw this type of issue, but with older releases of FreeIPA. It could happen with 389-ds versions < 1.3 (see https://pagure.io/freeipa/c/2563f6f59454b73373c5ef4117afc76984146187).
Which version of 389-ds is installed on your machines? # rpm -qa | grep 389
$ dpkg --list | grep "389" ii 389-ds-base 1.3.4.9-1 amd64 389 Directory Server suite - server ii 389-ds-base-libs 1.3.4.9-1 amd64 389 Directory Server suite - libraries ii slapi-nis 0.55-1 amd64 NIS Server and Schema Compatibility plugins for 389 Directory Server
Is the attribute nsds5replicareleasetimeout defined in the schema? You can check on each master with: # ldapsearch -x -h $MASTER -b cn=schema -s base -o ldif-wrap=no -LLL attributetypes| grep -i nsds5replicareleasetimeout
If the attribute is properly defined in the schema, the command should output 2 lines:
- one for the attribute definition, with attributetypes: (... NAME 'nsds5ReplicaReleaseTimeout' ...)
- one for the objectclass definition using this attribute, with objectclasses: (... NAME 'nsDS5Replica' ... MAY (... nsds5ReplicaReleaseTimeout ...) …)
No, I don’t get any search results at all.
Can you anticipate any issues with me modifying the schema and adding these attributes back in?
Thanks,
Mitch