Project

General

Profile

Actions

Bug #2559

closed

reduce log level in LDAP

Added by Francois BAYART over 12 years ago. Updated almost 10 years ago.

Status:
Released
Priority:
N/A
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

is-it possible to reduce the log verbose in OpenLDAP because there are most of "search" and logs grow very quickly.

-----snip here-----
slapd1223: conn=1002 op=2812 SRCH base="nodeGroupId=4a5bdc20-7943-4667-9922-915863c7d3b9,groupCategoryId=GroupRoot,ou=Rudder,cn=rudder-configuration" scope=0 deref=0 filter="(objectClass=*)"
-----snip here-----

Actions #1

Updated by Jonathan CLARKE over 12 years ago

  • Tracker changed from Question to Bug
  • Category set to 11
  • Status changed from New to In progress
  • Target version set to 2.3.8

Sure. The reason for this is that OpenLDAP's loglevel is set to "none stats" in /opt/rudder/etc/openldap/slapd.conf, which causes OpenLDAP to log several lines for each request that it handles.

I'm changing it be just "none" (critical messages only).

This will be released in 2.3.8 and 2.4.0. In the meantime, and for existing installations, please edit the "loglevel" line in /opt/rudder/etc/openldap/slapd.conf and restart OpenLDAP (/etc/init.d/slapd restart).

Actions #2

Updated by Jonathan CLARKE over 12 years ago

  • Status changed from In progress to Pending technical review
  • % Done changed from 0 to 100
Actions #3

Updated by Francois BAYART over 12 years ago

Jonathan CLARKE wrote:

This will be released in 2.3.8 and 2.4.0. In the meantime, and for existing installations, please edit the "loglevel" line in /opt/rudder/etc/openldap/slapd.conf and restart OpenLDAP (/etc/init.d/slapd restart).

ok perfect thx.

Actions #4

Updated by Nicolas CHARLES over 12 years ago

  • Status changed from Pending technical review to Released

This looks corect, thank you Jonathan !
However, why twice the same commit on different branches ?

Actions #5

Updated by Jonathan CLARKE over 12 years ago

Nicolas CHARLES wrote:

This looks corect, thank you Jonathan !
However, why twice the same commit on different branches ?

Hum, that's weird. It looks like I first commited on 2.4 branch, then wanted it on 2.3 branch. I'm not sure why I didn't do a cherry-pick... My bad.

Actions #6

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions #7

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions

Also available in: Atom PDF