Re: (ITS#4375) MOD operations not being logged

[quanah@stanford.edu]

On Wednesday 08 February 2006 16:17, Howard Chu wrote:
> Quanah Gibson-Mount wrote:
> > On Wednesday 08 February 2006 15:18, hyc@symas.com wrote:
> >> I don't see any processing error here. The mod operation is rejected
> >> before the Statslog statement is reached. The same can occur for all of
> >> the operation types if input validation fails before reaching the
> >> Statslog. In other words, Statslog only records properly formatted
> >> requests.
> >
> > I'm sorry, but what you are saying makes no sense.  There is a MOD line
> > here that is missing.  It should absolutely log what was trying to be
> > MODIFIED where the MODIFICATION failed.  If Statslog isn't doing this,
> > then it is flat out broken.
> >
> > The fact that only the failure is being logged, and not what entry the
> > MOD failed on is a BUG.  This didn't happen with the earlier 2.3
> > releases, i.e, this is new behavior with 2.3.19.
>
> The behavior I described has been part of every OpenLDAP 2.x release and
> likely every 1.x release as well. If a request doesn't get past input
> validation then it will not be logged by Statslog. I think the only
> reason you're seeing it now is because you've just brought a new client
> online that is submitting invalid modify requests that you never got
> before.

The *only* thing that has changed is the version of OpenLDAP software being 
used.  We haven't updated the process that writes to the account tree of the 
directory server in almost a year.

--Quanah