Slapd seems overly chatty in zimbra.log after upgrade to 5.0.6

[dionrowney]

Hi,

we just upgraded to 5.0.6 and have noticed that the logs are now mostly slapd debug data:

i.e.:

Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2012 SRCH attr=zimbraDomainName
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2012 SEARCH RESULT tag=101 err=0 nentries=0 text=
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2013 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=97bloomn@wht.com)(zimbraDomainName=97bloomn@wht.com))(zimbraMailStatus=enabled))"
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2013 SRCH attr=zimbraMailTransport
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2013 SEARCH RESULT tag=101 err=0 nentries=0 text=
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2014 SRCH base="" scope=2 deref=0 filter="(&(|(zimbraMailDeliveryAddress=wht.com)(zimbraDomainName=wht.com))(zimbraMailStatus=enabled))"
Jun 13 22:05:45 mail slapd[1687]: conn=329 op=2014 SRCH attr=zimbraMailTransport

and so on ... and on ... and on...

Any way to reduce this back to what it was before (not much)?

The file: /opt/zimbra/openldap/etc/openldap/slapd.conf has a line that says:

loglevel @@ldap_log_level@@

... I assume I can set it somewhere then? ...

Thanks

dion

[jholder]

Bug 28274 - LDAP Logging is too high

[dionrowney]

OK, this helps me how? It says the chatter is intentional. Does this mean there is no way for me lower the level?

Dion

[dijichi2]

/var/log/zimbra does seem to be pretty useless now due traffic. looks like they've turned it down in the bug report. might be nice to split zimbra.log out to seperate ldap/mail/auth/etc logs like unix normally does, it really makes things easier to read in the heat of the moment when things go wrong..

anyway quick fix is:
zmlocalconfig -e ldap_log_level=32768
or
zmlocalconfig -e ldap_log_level=0

[petrocc]

Originally Posted by dijichi2

/var/log/zimbra does seem to be pretty useless now due traffic. looks like they've turned it down in the bug report.

You can also use grep -v when digging to sort out stuff you don't want to see.

[dionrowney]

Thanks. the level = 0 did the trick. I certainly dont mind a bit of logging, but it appeared to be at the debug level and certainly more than I needed to see.

Many thanks.

[mmorse]

Originally Posted by dionrowney

Thanks. the level = 0 did the trick.

I would at least set it to the 5.0.5 value:
The keyword 'none', or the equivalent integer representation (32768 or 0x800), causes those messages that are always logged regardless of the configured loglevel to be output ie: critical stuff. In fact, if 'no' loglevel (0) is defined, absolutely no logging occurs, so at least the 'none' level is required to have high priority messages logged.

Originally Posted by mmorse

Safe to ignore, to debug stuff we are increasingly in need of more information:
Bug 27699 - Update LDAP logging to stats+sync
Bug 27207 - Log all access to LDAP

We're currently trying to find a middle ground via: Bug 28274 - LDAP Logging is too high


Old default: 32768 (OR 0x8000 OR none) would just log critical stuff

New defaults: 16640 = stats + sync, this is set only if 32768 was still present (in-case you set another value on your own).
Master: 32768 none (critical only)
Replicas: 49152 = none + sync = 32768 + 16384 (no stats but sync replica entries are logged)

For instance to set that replica value it would be:
zmlocalconfig -e ldap_log_level=49152
OR
zmlocalconfig -e ldap_log_level="none sync"

You can define it several ways (single interger in decimal or hexadecimal, or keywords) and then you can combine them - for instance these are equivalent:
loglevel 129
loglevel 0x81
loglevel 128 1
loglevel 0x80 0x1
loglevel acl trace

hexadecimal <> decimal conversion tool

The keyword any can be used as a shortcut to enable logging at all levels (equivalent to -1).

The keyword none, or the equivalent integer representation (32768 or 0x800), causes those messages that are always logged regardless of the configured loglevel to be output (specified & critical stuff). In fact, if no loglevel (or a 0 level) is defined, no logging occurs, so at least the none level is required to have high priority messages logged.

In short, 32768 (OR 0x8000 OR none) = only messages that get logged whatever log level is set, thus you get critical stuff.

5.0.5 style:
zmlocalconfig -e ldap_log_level=32768
zmcontrol stop/start

5.0.6 style:
zmlocalconfig -e ldap_log_level=16640
zmcontrol stop/start