[Date Prev][Date Next]
Re: (ITS#4375) MOD operations not being logged
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.
> On Friday 03 February 2006 10:44, you wrote:
>> firstname.lastname@example.org wrote:
>>> Full_Name: Quanah Gibson-Mount
>>> Version: 2.3.18
>>> OS: Solaris 8
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (188.8.131.52)
>>> 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:
> Then make a modification that changes a single valued attribute with two
> dn: uid=user.1,ou=peeps,dc=stanford,dc=edu
> displayName: Aaccf aab
> displayName: Aaccf aabasdf
> It will fail to log the MOD operation.
-- 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/