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

[hyc@symas.com]

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.

quanah@stanford.edu wrote:
> On Friday 03 February 2006 10:44, you wrote:
>   
>> quanah@stanford.edu wrote:
>>     
>>> Full_Name: Quanah Gibson-Mount
>>> Version: 2.3.18
>>> OS: Solaris 8
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (171.66.155.86)
>>>
>>>
>>> In looking at an error occurring on my master, I found that the MOD
>>> operation causing the error is not being logged at loglevel 256 like it
>>> should be.
>>>       
>> It's working in test004. You'll have to provide more info on how to
>> reproduce the problem.
>>     
>
> it is very trivial to reproduce.  Simply do the following:
>
> Set up a system with two subtrees.  For example, I have:
>
> ou=peons
> and
> ou=peeps
>
> Then make a modification that changes a single valued attribute with two 
> values:
>
> dn: uid=user.1,ou=peeps,dc=stanford,dc=edu
> changetype:modify
> replace:displayName
> displayName: Aaccf aab
> displayName: Aaccf aabasdf
>
> It will fail to log the MOD operation.
>
> --Quanah
>
>   


-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/