powered by Jive Software

Stop to log DEBUG trace

Hello, I’M using openfire 4.7.0

I have a lot of message from a Ldap connection, every second, likes openfire try to cocnect and retrieve info from LDAP repository, but do this every second.

2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - Starting LDAP search for username ‘jladiaz’…
2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - … search finished for username ‘jladiaz’.
2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - Processing relative LDAP SearchResult: ‘uid=jladiaz,ou=Users: null:null:{uid=uid: jladiaz}’
2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - Creating a DirContext in LdapManager.getContext() for baseDN ‘dc=vs-zmaster,dc=policia,dc=rionegro,dc=gov,dc=ar’…
2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - Created hashtable with context values, attempting to create context…
2021.11.09 07:51:40 DEBUG [pep-worker-2]: org.jivesoftware.openfire.ldap.LdapManager - … context created successfully, returning.
2021.11.09 07:51:40 DEBUG [socket_c2s-thread-4]: org.jivesoftware.openfire.ldap.LdapManager - Trying to find a user’s RDN based on their username: ‘medelmenico’. Field: ‘uid’, Base DN: ‘dc=vs-zmaster,dc=policia,dc=rionegro,dc=gov,dc=ar’ …
2021.11.09 07:51:40 DEBUG [socket_c2s-thread-4]: org.jivesoftware.openfire.ldap.LdapManager - Creating a DirContext in LdapManager.getContext() for baseDN ‘dc=vs-zmaster,dc=policia,dc=rionegro,dc=gov,dc=ar’…
2021.11.09 07:51:40 DEBUG [socket_c2s-thread-4]: org.jivesoftware.openfire.ldap.LdapManager - Created hashtable with context values, attempting to create context…
2021.11.09 07:51:40 DEBUG [socket_c2s-thread-4]: org.jivesoftware.openfire.ldap.LdapManager - … context created successfully, returning.

It is possible to stop this ? Doing this all time for al of users from ldap repository, so fast, and never stop.

append more data, when this happens the consumption of cpu is very high

There are changes in the logging mechanism in the current master branch.
So I think you should edit log4j2.xml in the openfire/lib directory.
There you have to disable debug logging in general.
You will find the docs here: Log4j – Configuring Log4j 2