#47539 Disabling DNA plug-in throws error 53
Closed: wontfix None Opened 10 years ago by nkinder.

Description of problem: Enabling DNA plugin throws the following error.

modifying entry "cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config"
ldap_modify: Server is unwilling to perform (53)
additional info: Changes result in an invalid DNA configuration.

Steps to Reproduce:
1. Install 389-ds-base-1.2.11.15-26 and run ldapmodify to enable DNA plugin.
2. Run ldapmodify to enable the DNA plug-in:

dn: cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: On

  1. Restart DS to load hte DNA plug-in.
  2. Run the same ldapmodify again.

Actual results: The plug-in is enabled at first, but the consecutive attempts
returns error 53.

modifying entry "cn=Distributed Numeric Assignment Plugin,cn=plugins,cn=config"
ldap_modify: Server is unwilling to perform (53)
additional info: Changes result in an invalid DNA configuration.

It looks like any change to the main DNA config entry when DNA is enabled is rejected at the pre-op stage in dna_parse_config_entry():


/* If this is the main DNA plug-in
- config entry, just bail. */
if (strcasecmp(getPluginDN(), slapi_entry_get_ndn(e)) == 0) {
    ret = DNA_FAILURE;
    goto bail;
}

Returning DNA_FAILURE will cause LDAP_UNWILLING_TO_PERFORM to be returned to the client. The purpose of dna_parse_config_entry() is to validate range config entries, which are children of the main DNA config entry. We want to skip validation of the main DNA config entry, but we shouldn't be rejecting the operation. I believe that the above code snippet should just return DNA_SUCCESS to allow validation to be skipped for the main DNA config entry.


Pushed to master. Thanks to Mark for the review!

master - d8c6e0c

Metadata Update from @nkinder:
- Issue assigned to nkinder
- Issue set to the milestone: 1.3.2 - 09/13 (September)

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/876

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata