Description of problem:
disk monitoring setting the wrong default error log level.
The error log level setting up should be 16384 not 266354688 while reaching to
set threshold by disk monitoring feature.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-21.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Setting nsslapd-disk-monitoring-logging-critical: off
ldapmodify -x -h localhost -p 31415 -D "cn=Directory Manager" -w Secret123 <<
EOF
dn: cn=config
changetype: modify
replace: nsslapd-disk-monitoring-logging-critical
nsslapd-disk-monitoring-logging-critical: off
EOF

2.enable_verbose_logging
ldapmodify x -h localhost -p 31415 -D "cn=Directory Manager" -w Secret123 <<
EOF
dn: cn=config
changetype: modify
replace: nsslapd-errorlog-level
nsslapd-errorlog-level: 8
EOF

3. Disk parameters
# cat disk_monitoring_vars
THRESHOLD=30
TOTAL_SIZE=35
USED_SIZE=0
AVAIL_SIZE=33
HALF_THR_FILL_SIZE=10
FULL_THR_FILL_SIZE=25
LOGDIR=/var/log/dirsrv/slapd-disk-monitoring

4. filling up space by half to trigger disk monitoring feature
dd if=/dev/zero of="/var/log/dirsrv/slapd-disk-monitoring/foo" bs=1M count=10
df -hP /var/log/dirsrv/slapd-disk-monitoring

[root@vm-idm-016 vm-idm-016.lab.eng.pnq.redhat.com]# dd if=/dev/zero
of="/var/log/dirsrv/slapd-disk-monitoring/foo" bs=1M count=10
10+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.0253913 s, 413 MB/s
[root@vm-idm-016 vm-idm-016.lab.eng.pnq.redhat.com]# df -hP
/var/log/dirsrv/slapd-disk-monitoring
Filesystem      Size  Used Avail Use% Mounted on
/dev/loop1       35M   11M   23M  33% /var/log/dirsrv/slapd-disk-monitoring

5. Now check the log level should goes back to default. AND in error logs it
does. BUT THE TEST CASE EXPECTS it to be "16384" which it consider the default
log level value.
ldapsearch -x -h localhost -p 31415 -D "cn=Directory Manager" -w Secret123 -b
"cn=config" -s base objectClass=* "nsslapd-errorlog-level" | grep -i
"nsslapd-errorlog-level"
266354688

6. Now the test case is checking for the "nsslapd-accesslog-logging-enabled"
configuration attribute, which should be turned "OFF" as expected but it is not
happening?
ldapsearch -x -h localhost -p 31415 -D "cn=Directory Manager" -w Secret123 -b
"cn=config" -s base objectClass=* nsslapd-accesslog-logging-enabled  | grep
"nsslapd-accesslog-logging-enabled" `

[root@vm-idm-016 vm-idm-016.lab.eng.pnq.redhat.com]# ldapsearch -x -h localhost
-p 31415 -D "cn=Directory Manager" -w Secret123 -b "cn=config" -s base
objectClass=* nsslapd-accesslog-logging-enabled  | grep
"nsslapd-accesslog-logging-enabled"
# requesting: nsslapd-accesslog-logging-enabled
nsslapd-accesslog-logging-enabled: on

=========================================
These are the settings done in the setup ::
=========================================
[root@vm-idm-016 vm-idm-016.lab.eng.pnq.redhat.com]# ldapsearch -x -h localhost
-p 31415 -D "cn=Directory Manager" -w Secret123 -b "cn=config" -s base
objectClass=* nsslapd-disk-monitoring  | grep "nsslapd-disk-monitoring"
# requesting: nsslapd-disk-monitoring
nsslapd-disk-monitoring: on


Major issues ::
1. The error log level setting up should be 16384 not 266354688
2. Error message should not get into the loop
3. Disk Monitor should turn off the access log

FULL ERROR LOGS - http://storm.idmqe.lab.eng.bos.redhat.com/qa/archive/beaker/R
HDS/RHEL75/389-ds-base-1.3.7.5-21.el7.x86_64/Tier1/output/Linux/20180416-131215
/disk_monitoring/disk_monitoring.run.out.12913

Note - These failures are from TET from Disk Monitoring feature.
This is discussed with Mark and he provided the information that fixing the
error log level with fix rest of the issues.