Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAGraDoEAzOO-2m7LxfksWMKXakxBQ6pjpT6_Gpuj=YY3_irOUw@mail.gmail.com>
References: 
 <CAGraDoEAPFs2kChzdPNnuwLPafinVBn_jY=EfSSRyEXqKqCy_g@mail.gmail.com>
	<56C228E0.60700@gmail.com>
	<CAGraDoEAzOO-2m7LxfksWMKXakxBQ6pjpT6_Gpuj=YY3_irOUw@mail.gmail.com>
Date: Thu, 18 Feb 2016 13:40:31 -0600
Message-ID: 
 <CAGraDoGyUK9LrKZAa996VD9SDO_Xgxi3A-79wwoK1Eh4O_n6Yg@mail.gmail.com>
Subject: Re: logging all incoming requests
From: Timothy Keith <timothy.g.keith@gmail.com>
To: users@directory.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
<timothy.g.keith@gmail.com> wrote:
> On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel L=C3=A9charny <elecharny@gmail.=
com> wrote:
>> Le 15/02/16 18:55, Timothy Keith a =C3=A9crit :
>>> I am attempting to do pass-through authentication from an OpenLDAP
>>> server.  I would to have debugging logs for all incoming requests.
>>>
>>> Tim
>> What kind of log do you want exactly ?
>>
>> If you want to have some logs about every received message, you can
>> modify the log4j.properties to set the
>> org.apache.directory.server.ldap.handlers.request package to DEBUG.
>>
>>
>> You'll receive logs like :
>>
>>         LOG.debug( "Received: {}", bindRequest );
>>         LOG.debug( "Handling request: {}", req );
>>         LOG.debug( "Handling compare request while ignoring referrals:
>> {}", req );
>>         LOG.debug( "Handling request: {}", req );
>>         LOG.debug( "Handling modify dn request while ignoring referrals:
>> {}", req );
>>         LOG.debug( "Handling request : {}", req );
>>         LOG.debug( "Handling single reply request: {}", req );
>>         LOG.debug( "Received: {}", unbindRequest );
>>
>> Four problems here :
>> - not all the messages get logged (Abandon)
>> - not all extended operations are logged, and they use a different logge=
r
>> - overall, the messages are not consistent
>> - you'll be flooded by logs you do'nt want.
>>
>> A better option would be to set a logger on
>> org.apache.directory.api.ldap.codec.api.LdapDecoder. You will then get
>> the fully decoded LDAP message like :
>>
>>                 LOG.debug( "Decoded LdapMessage : " + container );
>>
>>
>
> It would first help me to know how to configure the location for the
> wrapper.log on Microsoft Windows, and any other log files.   In
> wrapper.conf see a reference to "wrapper.log" file, but the single
> occurrence of that file was only written to during the install of
> Apache DS.
>
> Tim

Sometimes the search logs stop showing any result of ldapsearch
requests.     This Apache Directory Studio 2.0.0 on a a Windows 7
system.

Tim