Hide Forgot
Versions affected: 389-ds-base-1.2.11.15-22.el6_4.i686 (RHEL 6.4) 389-ds-base-1.2.11.15-29.el6.i686 (RHEL 6.5) Versions not affected: 389-ds-base-1.2.11.15-22.el6_4.x86_64 (RHEL 6.4) 389-ds-base-1.2.11.15-29.el6.x86_64 (RHEl 6.5) How reproducible: On 32bit RHEL 6.5: [jrusnack@dstet ~]$ ldapsearch -D "cn=directory manager" -w Secret123 -b "cn=config" -LLL nsslapd-disk-monitoring-threshold -s base dn: cn=config nsslapd-disk-monitoring-threshold: 2097152 [jrusnack@dstet ~]$ ldapmodify -D "cn=directory manager" -w Secret123 <<EOF > dn: cn=config > changetype: modify > replace: nsslapd-disk-monitoring-threshold > nsslapd-disk-monitoring-threshold: 3000000000 > EOF modifying entry "cn=config" [jrusnack@dstet ~]$ ldapsearch -D "cn=directory manager" -w Secret123 -b "cn=config" -LLL nsslapd-disk-monitoring-threshold -s base dn: cn=config nsslapd-disk-monitoring-threshold: -1294967296 [jrusnack@dstet ~]$ rpm -qa | grep 389-ds-base 389-ds-base-libs-1.2.11.15-29.el6.i686 389-ds-base-1.2.11.15-29.el6.i686 On 64bit RHEL 6.5: [jrusnack@dstet ~]$ ldapsearch -D "cn=directory manager" -w Secret123 -b "cn=config" -LLL nsslapd-disk-monitoring-threshold -s base dn: cn=config nsslapd-disk-monitoring-threshold: 2097152 [jrusnack@dstet ~]$ ldapmodify -D "cn=directory manager" -w Secret123 <<EOF > dn: cn=config > changetype: modify > replace: nsslapd-disk-monitoring-threshold > nsslapd-disk-monitoring-threshold: 3000000000 > EOF modifying entry "cn=config" [jrusnack@dstet ~]$ ldapsearch -D "cn=directory manager" -w Secret123 -b "cn=config" -LLL nsslapd-disk-monitoring-threshold -s base dn: cn=config nsslapd-disk-monitoring-threshold: 3000000000 [jrusnack@dstet ~]$ rpm -qa | grep 389-ds-base 389-ds-base-libs-1.2.11.15-29.el6.x86_64 389-ds-base-1.2.11.15-29.el6.x86_64
Credits for finding the bug to Sankar Ramlingam.
Upstream ticket: https://fedorahosted.org/389/ticket/47638
Fixed upstream
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1385.html