#49196 Autotune generates CRITICAL logs that are not critical
Closed: wontfix 7 years ago Opened 7 years ago by tbordaz.

Issue Description

Autotune main log such message

   [27/Mar/2017:19:34:46.910109416 +051800] - CRIT - ldbm_back_start - It is highly likely your memory configuration of all backends will EXCEED your systems memory.
   [27/Mar/2017:19:34:46.984890827 +051800] - CRIT - ldbm_back_start - In a future release this WILL prevent server start up. You MUST alter your configuration.
   [27/Mar/2017:19:34:47.084907023 +051800] - CRIT - ldbm_back_start - Total entry cache size: 42049536 B; dbcache size: 33305395 B; available memory size: 60301312 B; 
   [27/Mar/2017:19:34:47.168263704 +051800] - CRIT - ldbm_back_start - This can be corrected by altering the values of nsslapd-dbcachesize, nsslapd-cachememsize and nsslapd-dncachememsize

Package Version and Platform

389-ds-base

Steps to reproduce

  1. Install DS in on small memory VM
  2. trigger those message (memory pressure ?)
    3.

Actual results

CRITICAL logs

Expected results

WARN log


Metadata Update from @firstyear:
- Issue assigned to firstyear

7 years ago

Metadata Update from @firstyear:
- Custom field reviewstatus adjusted to review
- Custom field type adjusted to defect

7 years ago

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to ack (was: review)

7 years ago

commit 79307f5
To ssh://git@pagure.io/389-ds-base.git
85dcc19..79307f5 master -> master

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

7 years ago

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

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)

3 years ago

Login to comment on this ticket.

Metadata