[Date Prev][Date Next] [Chronological] [Thread] [Top]

Problems with log entries order

Writing a script for parsing openldap logs I found that, for some of my
connections, the BIND log entry precedes the corresponding ACCEPT entry
(which as far as i understand must logically precede the BIND)

example:
2016-01-25T12:54:02.131094+01:00 HOSTNAME slapd[15258]: conn=91596 op=0
BIND dn="" method=128
2016-01-25T12:54:02.131099+01:00 HOSTNAME slapd[15258]: conn=91596 op=0
RESULT tag=97 err=0 text=
2016-01-25T12:54:02.131103+01:00 HOSTNAME slapd[15258]: conn=91596 fd=93
ACCEPT from [CUT]

slapd is started with the '-l local4' parameter, and rsyslogd is
configured to send local4.* to the openldap.log file

suspecting some rsyslogd problems i tried running slapd using the "-d
256" parameter, but in the output i found

56a6202b conn=1004 op=0 BIND dn="" method=128
56a6202b conn=1004 op=0 RESULT tag=97 err=0 text=
56a6202b conn=1004 fd=13 ACCEPT from [CUT]

Is there any way to guarantee openldap to generate ordered logs?

thanks,
dario