Re: How to find out what is doing to many ldap queries
[
Date Prev][Date Next]
[
Thread Prev][Thread Next]
Re: How to find out what is doing to many ldap queries
- From: Arthur de Jong <arthur [at] arthurdejong.org>
- To: "Riha, Marek" <Marek.Riha [at] t-systems.com>, "nss-pam-ldapd-users [at] lists.arthurdejong.org" <nss-pam-ldapd-users [at] lists.arthurdejong.org>
- Subject: Re: How to find out what is doing to many ldap queries
- Date: Thu, 07 Dec 2017 22:29:49 +0100
On Thu, 2017-12-07 at 18:06 +0000, Riha, Marek wrote:
> I set debug mode for nscd and I see a lot of these messages:
nscd maintains a system cache for name lookups. If the listed users
cannot be found with
getent passwd USERNAME
that aspect of caching can be configure in nscd.conf with the
negative-time-to-live option. If the user is found caching in nscd can
be configured with positive-time-to-live.
However, nscd does not have anything specific to do with LDAP (it will
also cache /etc/passwd entries). The connection to the LDAP server is
configured via nslcd (does not do caching except for one specific
case).
> Is there possibility How to find out what is doing to many ldap
> queries ?
The logs you provided already provide tha PID of the process that is
performing the lookups. That should narrow it down a bit.
If you run nslcd in debug mode it will similarly report the PID of the
process that is making the requests (in your case it is likely that a
lot of requests are made through nscd).
Hope this helps,
--
-- arthur - arthur@arthurdejong.org - https://arthurdejong.org/ --
--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
https://lists.arthurdejong.org/nss-pam-ldapd-users/