LDAP logging is set to DEBUG on production CNs
This is far too verbose for production environment. Needs to be adjusted to INFO or ERROR
#1 Updated by Rob Nahf about 5 years ago
- Assignee set to Jing Tao
- Target version changed from CCI-2.3.6 to CCI-2.3.5
The log4j.properties file in dataone-cn-metacat seems to control at least part of this, and we are deploying a new one in CCI 2.3.5.
If it's a simple change, maybe we can reduce the log level for metacat replication and hazelcast from DEBUG to INFO or WARN before 2.3.5 tagging.
#5 Updated by Dave Vieglais about 5 years ago
ldap searches are being logged to /var/log/syslog at a rate of about 1 - 2k lines / sec:
tail -f syslog | pv -l -i10 -r >/dev/null
Loglevel is set to 0 for slapd (should probably be set to "none") so not sure what is doing the logging.
Log those messages that are logged regardless of the configured loglevel. This differs from setting the
log level to 0, when no logging occurs. At least the None level is required to have high priority messages logged.