I meant to say:

"are you sure this is the ldap_cachemgr which does that? I vaguely remember seeing something simliar, but cannot tell whether it was actually ldap_cachemgr or nscd."

________________________________

Von: openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org [mailto:openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org] Im Auftrag von Kick, Claus Gesendet: Donnerstag, 20. März 2008 16:12 An: openldap-technical@openldap.org Betreff: AW: Solaris 10 Client ; Openldap 2.4 Server;supportedControl supportedsaslmechanisms

Hello,

are you sure this is the ldap_cachemgr which does that? I vaguely remember seeing something different, but cannot tell whether it was actually ldap_cachemgr or nscd.

Are you using nscd?

(svcs -a |grep name-service-cache)

Cheers, Claus

________________________________

Von: openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org [mailto:openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org] Im Auftrag von Mark S Gesendet: Dienstag, 18. März 2008 18:23 An: openldap-technical@openldap.org Betreff: Solaris 10 Client ; Openldap 2.4 Server;supportedControl supportedsaslmechanisms

I am running a Solaris 10 x86 environment and have built Openldap 2.4.8 as by LDAP server platform.

On the client side I have run the following ldapclient command to configure my clients;

ldapclient manual -v -a credentialLevel=anonymous \ -a authenticationMethod=none \ -a defaultsearchbase='dc=nyc,dc=example,dc=com' \ -a defaultServerList=10.0.0.1 \ -a serviceSearchDescriptor=passwd:ou=people,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=group:ou=group,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=services:ou=services,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=protocols:ou=protocols,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=rpc:ou=rpc,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=hosts:ou=hosts,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=networks:ou=networks,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=netgroup:ou=netgroup,dc=nyc,dc=example,dc=com?one

I have ended up with the following /var/ldap/ldap_client_file

NS_LDAP_FILE_VERSION= 2.0 NS_LDAP_SERVERS= 10.0.0.1 NS_LDAP_SEARCH_BASEDN= dc=nyc,dc=example,dc=com NS_LDAP_AUTH= none NS_LDAP_CACHETTL= 0 NS_LDAP_CREDENTIAL_LEVEL= anonymous NS_LDAP_SERVICE_SEARCH_DESC= passwd:ou=people,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= group:ou=group,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= services:ou=services,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= protocols:ou=protocols,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= rpc:ou=rpc,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= hosts:ou=hosts,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= networks:ou=networks,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= netgroup:ou=netgroup,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= automount:ou=automount,dc=nyc,dc=example,dc=com?one

In general all is working fine. My one concerns is that when I have been monitoring the ldap logs i see the below query over and over again

Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 848112 local4.debug] conn=9423 fd=38 ACCEPT from IP=10.0.1.182:42757 (IP=0.0.0.0:389) Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 469902 local4.debug] conn=9423 op=0 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 744844 local4.debug] conn=9423 op=0 SRCH attr=supportedControl supportedsaslmechanisms Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 167594 local4.debug] conn=9423 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text= Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 218904 local4.debug] conn=9423 op=1 UNBIND Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 952275 local4.debug] conn=9423 fd=38 closed

Does anyone know why the Solaris ldap_cachemgr process keeps performing this query over and over again and what I might do to stop it. Thanks!

Hello,

If this is the only query happening, then no. As far as I can remember, I only saw this once after every client restart, or periodically with (probably) some cache refresh. But this is a bit hazy in memory, sorry.

Cheers, Claus

________________________________

Von: Mark S [mailto:tokenrain@gmail.com] Gesendet: Donnerstag, 20. März 2008 16:24 An: Kick, Claus Cc: openldap-technical@openldap.org Betreff: Re: Solaris 10 Client ; Openldap 2.4 Server; supportedControl supportedsaslmechanisms

I am running nscd as well. I would still have the question do you know why nscd would be making this query over and over again?

On Thu, Mar 20, 2008 at 11:17 AM, Kick, Claus claus.kick@siemens.com wrote:

I meant to say: "are you sure this is the ldap_cachemgr which does that? I vaguely remember seeing something simliar, but cannot tell whether it was actually ldap_cachemgr or nscd." ________________________________ Von: openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org [mailto:openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org] Im Auftrag von Kick, Claus Gesendet: Donnerstag, 20. März 2008 16:12 An: openldap-technical@openldap.org Betreff: AW: Solaris 10 Client ; Openldap 2.4 Server;supportedControl supportedsaslmechanisms

Hello, are you sure this is the ldap_cachemgr which does that? I vaguely remember seeing something different, but cannot tell whether it was actually ldap_cachemgr or nscd. Are you using nscd? (svcs -a |grep name-service-cache) Cheers, Claus ________________________________ Von: openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org [mailto:openldap-technical-bounces+claus.kick=siemens.com@OpenLDAP.org] Im Auftrag von Mark S Gesendet: Dienstag, 18. März 2008 18:23 An: openldap-technical@openldap.org Betreff: Solaris 10 Client ; Openldap 2.4 Server;supportedControl supportedsaslmechanisms I am running a Solaris 10 x86 environment and have built Openldap 2.4.8 as by LDAP server platform. On the client side I have run the following ldapclient command to configure my clients; ldapclient manual -v -a credentialLevel=anonymous \ -a authenticationMethod=none \ -a defaultsearchbase='dc=nyc,dc=example,dc=com' \ -a defaultServerList=10.0.0.1 \ -a serviceSearchDescriptor=passwd:ou=people,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=group:ou=group,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=services:ou=services,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=protocols:ou=protocols,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=rpc:ou=rpc,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=hosts:ou=hosts,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=networks:ou=networks,dc=nyc,dc=example,dc=com?one \ -a serviceSearchDescriptor=netgroup:ou=netgroup,dc=nyc,dc=example,dc=com?one I have ended up with the following /var/ldap/ldap_client_file NS_LDAP_FILE_VERSION= 2.0 NS_LDAP_SERVERS= 10.0.0.1 NS_LDAP_SEARCH_BASEDN= dc=nyc,dc=example,dc=com NS_LDAP_AUTH= none NS_LDAP_CACHETTL= 0 NS_LDAP_CREDENTIAL_LEVEL= anonymous NS_LDAP_SERVICE_SEARCH_DESC= passwd:ou=people,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= group:ou=group,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= services:ou=services,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= protocols:ou=protocols,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= rpc:ou=rpc,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= hosts:ou=hosts,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= networks:ou=networks,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= netgroup:ou=netgroup,dc=nyc,dc=example,dc=com?one NS_LDAP_SERVICE_SEARCH_DESC= automount:ou=automount,dc=nyc,dc=example,dc=com?one In general all is working fine. My one concerns is that when I have been monitoring the ldap logs i see the below query over and over again Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 848112 local4.debug] conn=9423 fd=38 ACCEPT from IP=10.0.1.182:42757 (IP=0.0.0.0:389) Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 469902 local4.debug] conn=9423 op=0 SRCH base="" scope=0 deref=0 filter="(objectClass=*)" Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 744844 local4.debug] conn=9423 op=0 SRCH attr=supportedControl supportedsaslmechanisms Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 167594 local4.debug] conn=9423 op=0 SEARCH RESULT tag=101 err=0 nentries=1 text= Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 218904 local4.debug] conn=9423 op=1 UNBIND Mar 18 12:10:23 ldap1.nyc.example.com slapd[6642]: [ID 952275 local4.debug] conn=9423 fd=38 closed Does anyone know why the Solaris ldap_cachemgr process keeps performing this query over and over again and what I might do to stop it. Thanks!