directory server fails to start because maxdisksize (nsslapd-*log-logmaxdiskspace ) is recognized incorrectly

Solution Verified - Updated -

Issue

Directory server instances fails to start with following errors.

[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]
  • The phenomenon happens after updating 389-ds-base package to 1.3.6.1-16.el7.
  • The directory server instances were able to start without such errors before updating the 389-ds-base package.
  • Freshly installed directory server 10 instance on RHEL 7.4 fails to start after setting maximum log size (nsslapd-*log-logmaxlogsize) .
  • It seems that the maximum disk size (nsslapd-*log-logmaxdiskspace ) is recognized incorrectly.

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Directory Server 10
  • 389-ds-base-1.3.6.1-16.el7 or later version

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.