Hello,
I find sometimes order of event in openldap logs as: BIND RESULT ACCEPT SRCH base SRCH attr= SEARCH RESULT closed
Configured rsyslog as: $template myTemplate,"%timegenerated:::date-rfc3339% %timereported:::date-rfc3339% %msg%\n" local4.* /var/log/rsyslog.log;myTemplate
But I believe correct order should be: Accept Bind result srch base unbind closed
What cant be the reason, is it related to openldap logging mechanism or Logger rsyslog.
Amit wrote:
I find sometimes order of event in openldap logs as: BIND RESULT ACCEPT SRCH base SRCH attr= SEARCH RESULT closed [..] But I believe correct order should be: Accept Bind result srch base unbind closed
Multiple connections can be logged in different states. Make sure you really observe a single connection by looking at the same conn=.. value.
Ciao, Michael.
Dear Michel,
Thanks for response. yes conn= are same. These are for single connection only.
Thanks Amit
On 07/25/2017 06:21 PM, Michael Ströder wrote:
Amit wrote:
I find sometimes order of event in openldap logs as: BIND RESULT ACCEPT SRCH base SRCH attr= SEARCH RESULT closed [..] But I believe correct order should be: Accept Bind result srch base unbind closed
Multiple connections can be logged in different states. Make sure you really observe a single connection by looking at the same conn=.. value.
Ciao, Michael.
On 25. juli 2017 09:10, Amit wrote:
I find sometimes order of event in openldap logs as: BIND RESULT ACCEPT (...)
What cant be the reason, is it related to openldap logging mechanism or Logger rsyslog.
You can or could be out-of-order logging when different operations on the connection are handled by different threads. In particular if you have an old OpenLDAP release. We've fixed some, but I don't know if we did them all. I remember leaving one case as it was because fixing it would mean delay releasing a lock. (ITS#7543)
Hello Hallvard,
Huge thanks for response.
But still in which release we have fixed the Issue. And which release is having the Issues?
Which Bug-Fix has done this change?
Thanks
Amit
On 07/25/2017 07:13 PM, Hallvard Breien Furuseth wrote:
On 25. juli 2017 09:10, Amit wrote:
I find sometimes order of event in openldap logs as: BIND RESULT ACCEPT (...)
What cant be the reason, is it related to openldap logging mechanism or Logger rsyslog.
You can or could be out-of-order logging when different operations on the connection are handled by different threads. In particular if you have an old OpenLDAP release. We've fixed some, but I don't know if we did them all. I remember leaving one case as it was because fixing it would mean delay releasing a lock. (ITS#7543)
openldap-technical@openldap.org