389-ds-base

#50153 default of "nsslapd-errorlog-maxlogsperdir: 1" causing huge log files
Closed: wontfix by mreynolds. Opened by mreynolds.

Closed: wontfix
Reopen Issue

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1643587

Description of problem:
DS default of not rotating error log file can lead to filling up /var
filesystem with disastrous results
Version-Release number of selected component (if applicable):
389-ds-base-1.3.7.5-25.el7_5.x86_64
389-ds-base-1.3.6.1-16.el7.x86_64
389-ds-base-1.3.6.1-28.el7
How reproducible:
consistent
Steps to Reproduce:
1. Install IPA
2. Have default of "nsslapd-errorlog-maxlogsperdir: 1"
Actual results:
Large log files if many errors are reported, leading to possible crashes when
/var fills up
Expected results:
Either truncation of errorlog file at "nsslapd-errorlog-maxlogsize: 100" or a
default of at least 2 files for rotation.
Additional info:
1) Documentation of default:
   "3.1.1.90. nsslapd-errorlog-maxlogsperdir (Maximum Number of Error Log
Files)"
   https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/ht
ml/configuration_command_and_file_reference/core_server_configuration_reference
#cnconfig-nsslapd_errorlog_maxlogsperdir_Maximum_Number_of_Error_Log_Files
   "This attribute sets the total number of error logs that can be contained in
the directory where the error log is stored. ... The default is 1 log. If this
default is accepted, the server does not rotate the log, and it grows
indefinitely."

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1643587

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

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.3.9 (was: 0.0 NEEDS_TRIAGE)

https://pagure.io/389-ds-base/pull-request/50154

commit ca13f42da4d49fd30200fed960e1ad2d0fd1c763 - master

e86c2b2f4..f38a03d8a 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

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

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/3212

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)
Metadata
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.