RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1488836 - directory server fails to start because maxdisksize (nsslapd-*log-logmaxdiskspace ) is recognized incorrectly
Summary: directory server fails to start because maxdisksize (nsslapd-*log-logmaxdisks...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2017-09-06 10:03 UTC by Reona Yamamoto
Modified: 2021-08-30 13:46 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.7.5-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 14:19:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2433 0 None closed directory server fails to start because maxdisksize (nsslapd-*log-logmaxdiskspace ) is recognized incorrectly 2020-10-30 07:13:08 UTC
Red Hat Knowledge Base (Solution) 3173841 0 None None None 2017-09-06 11:30:33 UTC
Red Hat Product Errata RHBA-2018:0811 0 None None None 2018-04-10 14:20:43 UTC

Description Reona Yamamoto 2017-09-06 10:03:53 UTC 
Description of problem:

A directory server instance fails to start up with the following error.

----
[04/Sep/2017:20:18:14.530818672 +0900] - ERR - log_set_logsize - Invalid value for Maximum log size:Maxlogsize:300 (MB) exceeds Maxdisksize:100 (MB)
[04/Sep/2017:20:18:14.535062585 +0900] - ERR - dse_read_one_file - The entry cn=config in file /etc/dirsrv/slapd-ds2/dse.ldif (lineno: 10) is invalid, error code 1 (Operations error) -
[04/Sep/2017:20:18:14.569222415 +0900] - ERR - init_dse_file - Could not load config file [dse.ldif]
----

As far as I confirmed, this happens with the following conditions a, b and c.

a. package version is 389-ds-base-1.3.6.1-16.el7.
b. value of parameters.

  nsslapd-*log-maxlogsize is greater than 100 (MB).

c. The order of parameters in cn=config .

- The problem happens.
---
dn: cn=config
(snip)
nsslapd-errorlog-maxlogsize: 300
nsslapd-errorlog-logmaxdiskspace: 500
(snip)
---

- The problem does not happen.
---
dn: cn=config
(snip)
nsslapd-errorlog-logmaxdiskspace: 500
nsslapd-errorlog-maxlogsize: 300
(snip)
---

Version-Release number of selected component (if applicable):
389-ds-base-1.3.6.1-16.el7.x86_64
Red Hat Directory Server 10

How reproducible:
Always

Steps to Reproduce:
1) Prepare a Directory Server Instance with 389-ds-base-1.3.6.1-16.el7. (RHDS 10)
2) Stop the directory server instance.
3) Add the following two lines to cn=config entry in dse.ldif.

---
dn: cn=config
(snip)
nsslapd-errorlog-maxlogsize: 300
nsslapd-errorlog-logmaxdiskspace: 500
(snip)
----
4) Start the instance but it fails.

[04/Sep/2017:20:18:14.530818672 +0900] - ERR - log_set_logsize - Invalid value for Maximum log size:Maxlogsize:300 (MB) exceeds Maxdisksize:100 (MB)
[04/Sep/2017:20:18:14.535062585 +0900] - ERR - dse_read_one_file - The entry cn=config in file /etc/dirsrv/slapd-ds2/dse.ldif (lineno: 10) is invalid, error code 1 (Operations error) -
[04/Sep/2017:20:18:14.569222415 +0900] - ERR - init_dse_file - Could not load config file [dse.ldif]

5) Edit the dse.ldif file again and change the order of attributes.

---
dn: cn=config
(snip)
nsslapd-errorlog-logmaxdiskspace: 500
nsslapd-errorlog-maxlogsize: 300
(snip)
----

6) Start the instance again. It can start up without errors.

[04/Sep/2017:20:19:51.699856551 +0900] - INFO - main - 389-Directory/1.3.6.1 B2017.158.1159 starting up
[04/Sep/2017:20:19:51.712940094 +0900] - INFO - ldbm_instance_config_cachememsize_set - force a minimal value 512000
[04/Sep/2017:20:19:51.721326096 +0900] - NOTICE - ldbm_back_start - found 1015004k physical memory
[04/Sep/2017:20:19:51.723214606 +0900] - NOTICE - ldbm_back_start - found 703204k available
[04/Sep/2017:20:19:51.725416288 +0900] - NOTICE - ldbm_back_start - cache autosizing: db cache: 40600k
[04/Sep/2017:20:19:51.727704792 +0900] - NOTICE - ldbm_back_start - cache autosizing: userRoot entry cache (1 total): 65536k
[04/Sep/2017:20:19:51.732686002 +0900] - NOTICE - ldbm_back_start - total cache size: 110854274 B;
[04/Sep/2017:20:19:51.848819439 +0900] - INFO - slapd_daemon - slapd started.  Listening on All Interfaces port 12389 for LDAP requests

Actual results:
DS instance fails to start.

Expected results:
DS instance did not to start.

Additional info:
The phenomenon doesn't occur with old 389-ds-base package like 389-ds-base-1.3.5.10-18.el7_3.
This problem was reported by a customer who updated the 389-ds-base to 389-ds-base-1.3.6.1-16.el7.
Comment 3 wibrown@redhat.com 2017-09-07 00:35:32 UTC 
Upstream ticket:
https://pagure.io/389-ds-base/issue/49374
Comment 5 Simon Pichugin 2017-11-30 10:03:46 UTC 
======================== test session starts ========================
platform linux -- Python 3.6.3, pytest-3.3.0, py-1.5.2, pluggy-0.6.0 -- /opt/rh/rh-python36/root/usr/bin/python3
cachedir: .cache
metadata: {'Python': '3.6.3', 'Platform': 'Linux-3.10.0-768.el7.x86_64-x86_64-with-redhat-7.5-Maipo', 'Packages': {'pytest': '3.3.0', 'py': '1.5.2', 'pluggy': '0.6.0'}, 'Plugins': {'metadata': '1.5.1', 'html': '1.16.0'}}
389-ds-base: 1.3.7.5-9.el7
nss: 3.34.0-0.1.beta1.el7
nspr: 4.17.0-1.el7
openldap: 2.4.44-9.el7
svrcore: 4.1.3-2.el7

rootdir: /mnt/tests/rhds/tests/upstream/ds, inifile:
plugins: metadata-1.5.1, html-1.16.0
collected 1 item

dirsrvtests/tests/suites/config/regression_test.py::test_maxbersize_repl PASSED                                                                                                        [100%]

======================== 1 passed in 22.77 seconds ========================
Comment 8 errata-xmlrpc 2018-04-10 14:19:40 UTC 
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.

https://access.redhat.com/errata/RHBA-2018:0811
Note You need to log in before you can comment on or make changes to this bug.