Access Log Content218 Red Hat Directory Server Configuration, Command, and File Reference • May 2005Abandon MessageThe abandon message, in this case [21/Apr/2005:11:39:52 -0700] conn=12op=2 ABANDON targetop=1 msgid=2 nentries=0 etime=0, indicates that anoperation has been aborted, where nentries=0 indicates the number of entriessent before the operation was aborted, etime=0 value indicates how much time(in seconds) had elapsed, and targetop=1 corresponds to an operation valuefrom a previously initiated operation (that appears earlier in the access log).There are two possible log ABANDON messages, depending on whether the messageID succeeds in locating which operation was to be aborted. If the message IDsucceeds in locating the operation (the targetop) then the log will read as above.However, if the message ID does not succeed in locating the operation or if theoperation had already finished prior to the ABANDON request being sent, then thelog will read as follows:[21/Apr/2005:11:39:52 -0700] conn=12 op=2 ABANDONtargetop=NOTFOUND msgid=2where targetop=NOTFOUND indicates the operation to be aborted was either anunknown operation or already complete.Message IDThe message ID, in this case msgid=2, is the LDAP operation identifier, asgenerated by the LDAP SDK client. The message ID may have a different valuethan the Red Hat Directory Server Operation Number but identifies the sameoperation. The message ID is used in the context of an ABANDON operation and tellsthe user which client operation is being abandoned.SASL Multi-Stage Bind LoggingIn Directory Server, logging for multi-stage binds is explicit. Each stage in thebind process is logged, and, where appropriate, the progress statement SASLbind in progress is included.In logging a SASL bind, the sasl method is followed by the LDAP versionnumber (see “Version Number”) and the SASL mechanism used, as shown belowwith the GSS-API mechanism.NOTE The Directory Server operation number starts counting at 0, and, inthe majority of LDAP SDK/client implementations, the message IDnumber starts counting at 1, which explains why the message ID isfrequently equal to the Directory Server operation number plus 1.
