You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Timothy Keith <ti...@gmail.com> on 2016/02/15 18:55:12 UTC
logging all incoming requests
I am attempting to do pass-through authentication from an OpenLDAP
server. I would to have debugging logs for all incoming requests.
Tim
Re: logging all incoming requests
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 19/02/16 03:27, Timothy Keith a écrit :
> On Thu, Feb 18, 2016 at 1:40 PM, Timothy Keith
> <ti...@gmail.com> wrote:
>> On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
>> <ti...@gmail.com> wrote:
>>> On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>> 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
>
> Is it generally recommended to run Apache DS on Linux vs Windows?
No, not at all.
We prefer linux because we don't have to pay to have an OS installed on
our machines, that's all, but we provide builds for windows because it's
widely used, like it or not.
Re: logging all incoming requests
Posted by Kiran Ayyagari <ka...@apache.org>.
On Fri, Feb 19, 2016 at 7:57 AM, Timothy Keith <ti...@gmail.com>
wrote:
> On Thu, Feb 18, 2016 at 1:40 PM, Timothy Keith
> <ti...@gmail.com> wrote:
> > On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
> > <ti...@gmail.com> wrote:
> >> On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com>
> wrote:
> >>> Le 15/02/16 18:55, Timothy Keith a écrit :
> >>>> 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
> logger
> >>> - 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
>
>
> Is it generally recommended to run Apache DS on Linux vs Windows?
>
> It works fine on both but if I have to pick a side it is Linux (obviously
;)
On Linux you have the flexibility of running it using shell script without
depending on the wrapper.
> Tim
>
Kiran Ayyagari
Re: logging all incoming requests
Posted by Timothy Keith <ti...@gmail.com>.
On Thu, Feb 18, 2016 at 1:40 PM, Timothy Keith
<ti...@gmail.com> wrote:
> On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
> <ti...@gmail.com> wrote:
>> On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>> Le 15/02/16 18:55, Timothy Keith a écrit :
>>>> 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 logger
>>> - 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
Is it generally recommended to run Apache DS on Linux vs Windows?
Tim
Re: logging all incoming requests
Posted by Kiran Ayyagari <ka...@apache.org>.
On Fri, Feb 19, 2016 at 1:10 AM, Timothy Keith <ti...@gmail.com>
wrote:
> On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
> <ti...@gmail.com> wrote:
> > On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com>
> wrote:
> >> Le 15/02/16 18:55, Timothy Keith a écrit :
> >>> 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
> logger
> >> - 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.
>
and there are no errors in the logs in this situation?
>
> Tim
>
Kiran Ayyagari
Re: logging all incoming requests
Posted by Timothy Keith <ti...@gmail.com>.
On Mon, Feb 15, 2016 at 4:36 PM, Timothy Keith
<ti...@gmail.com> wrote:
> On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
>> Le 15/02/16 18:55, Timothy Keith a écrit :
>>> 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 logger
>> - 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
Re: logging all incoming requests
Posted by Timothy Keith <ti...@gmail.com>.
On Mon, Feb 15, 2016 at 1:37 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
> Le 15/02/16 18:55, Timothy Keith a écrit :
>> 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 logger
> - 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
Re: logging all incoming requests
Posted by Emmanuel Lécharny <el...@gmail.com>.
Le 15/02/16 18:55, Timothy Keith a écrit :
> 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 logger
- 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 );