reassign 309026 slapd thanks Hi again,
On Sat, May 14, 2005 at 10:56:45AM +0200, Klaus Ethgen wrote: > Am Sa den 14. Mai 2005 um 10:07 schrieb Steve Langasek: > > I'm not sure what you mean by this bug. Are you reporting a bug against the > > software running on your client system, or on your server system? > Well, the problem is on the client. But I'm not completely sure if this > bug is a client or a server bug. Ok, sure. > > But your strace shows that all the time is spent waiting for data from the > > server, which sounds like a server bug. While cron is hanging, do other > > queries (using ldapsearch, for example) still work from this system? Can > Yes, no problem. only cron is hanging and all other applications > including nss and pam is working well. Ok. Are you using pam_ldap on this system? I have heard a report of pam_ldap causing performance problems against slapd 2.2.23 because of unnecessarily complex queries that don't match the schema in use and miss the indexing. > > you forward us a copy of your /etc/ldap/slapd.conf? - > I attache one to this mail. Thanks. > > What is the exact version of slapd running on your sarge system? > 2.2.23-1 Ok. I don't think there have been any improvements between 2.2.23-1 and 2.2.23-5 that will help you directly, now that you've upgraded; however, there are a few more things to check. Do you have a /var/lib/ldap/DB_CONFIG file on this system? If not, I recommend that you read <http://www.stanford.edu/services/directory/openldap/configuration/bdb-config-42.html> about BDB tuning with OpenLDAP, and create this file. As I understand it, you will need to dump and reload your directory in order for this file to take effect if it was not already present. If you do have a DB_CONFIG file, you should not need to dump and reload the directory, but there may still be some tuning that needs to be done on the server. If none of that helps, you may want to turn on debugging on the server, to see what queries are being sent that take this long to return. > ####################################################################### > # Specific Directives for database #1, of type bdb: > # Database specific directives apply to this databasse until another > # 'database' directive occurs > database bdb > > # The base of your directory in database #1 > suffix "dc=xxxxxx,dc=de" > # Where the database file are physically stored for database #1 > directory "/var/lib/ldap" > # Indexing options for database #1 > index objectClass eq You probably want to add some other indices here for performance reasons and re-run slapindex. The ones I've used for nss_ldap systems are: index uid pres,eq index cn,sn pres,eq,sub index objectClass eq index uidNumber pres,eq index gidNumber pres,eq How many entries do you have in this directory, btw? Unfortunately, there are limits to how automatic we can make the tuning of the slapd package. (And I am still hoping that this is just a tuning problem for you.) 2.2.23-5 is better than 2.2.23-1, but still not perfect; I hope we can make -6 better still for sarge. Thanks, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
