#49673 nsslapd-cachememsize can't be set to a value bigger than 2^32-1
Closed: wontfix 4 years ago Opened 4 years ago by vashirov.

Issue Description

With and without autotuning nsslapd-cachememsize can't be set to a value bigger than 2^32-1:

ldap_modify: Server is unwilling to perform (53)
        additional info: Error: value 2147483649 for attr nsslapd-cachememsize is greater than the maximum 2147483647

Package Version and Platform

389-ds-base-1.4.0.9-1.fc28.x86_64

Steps to reproduce

  1. Set nsslapd-cache-autosize: 0
  2. Change nsslapd-cachememsize
ldapmodify -D "cn=Directory Manager" -w Secret123 
dn: cn=userRoot,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-cachememsize
nsslapd-cachememsize: 2147483649

modifying entry "cn=userRoot,cn=ldbm database,cn=plugins,cn=config"
ldap_modify: Server is unwilling to perform (53)
        additional info: Error: value 2147483649 for attr nsslapd-cachememsize is greater than the maximum 2147483647

Expected results

Accepted value should be in range according to the documentation:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html-single/configuration_command_and_file_reference/#nsslapd_cachememsize

This happens only in 1.4.x.


Metadata Update from @mreynolds:
- Issue assigned to mreynolds

4 years ago

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4.0

4 years ago

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

4 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/2732

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)

2 years ago

Login to comment on this ticket.

Metadata