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

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

quanah@stanford.edu wrote:
> --On Friday, February 03, 2006 10:44 AM -0800 Howard Chu <hyc@symas.com> 
> 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) (
>>> 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 only happens when a single valued attribute is given multiple values on 
> the MOD, causing it to fail.  All other MOD ops are logged correctly.  I'm 
> working on setting up a reproducible scenario.

The Statslog message you're looking for is only logged after a number of 
validity checks have passed. If the checks fail the operation is aborted 
before getting to the Statslog. This is by design, most of the 
operations will abort on invalid input and not log the offending 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/