-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hoi,
Am Sa den 14. Mai 2005 um 11:19 schrieb Steve Langasek: > Ok. Are you using pam_ldap on this system? I have heard a report of Yes I do. All my normal users are in ldap. > 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. That might match. When I have a user crontab the daemon freeze faster. But it also freeze (on the same position) when I have no user crontabs. > 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, Well I did check. And the bug was also with 2.2.23-1. I did not go further back but the bug only happens few weeks now. > there are a few more things to check. Do you have a /var/lib/ldap/DB_CONFIG No. > 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. So this is server tuning as I understand. > 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. As this might go longer I have to move it to monday evening. > 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 I'l try... > How many entries do you have in this directory, btw? Only 9 users so this shouldn't be a performance problem for the server. > 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. Me too. But I wonder because the computers are only one switch from each other and there are few users only. What me makes confuse is that it start some weeks ago. Unfortunality I do not exactely know when. I only notice it as the backup was not startet nightly. Many thanks for the help. I hope fixing this problem right fast. I did wrote a small perl daemon now which will restart cron in the case it is not reacting. But this is only a bad hack to minimal doing the necesary work. Gruß Klaus - -- Klaus Ethgen http://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[EMAIL PROTECTED]> Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iQEVAwUBQoXJO5+OKpjRpO3lAQIDOQgAnYjw/VNrwypN78/sWnPGByvKWRrP+DHL AnlNkcMX73GmItBvg3u4YYzw+b4bBx0MaAGeUwNHY2lTUa0rOlmPxkCzyJrmutjQ wgSuL7RuZqb1IPmMW9yKB21/q/q4keG5jJLOjZigHY1gd3fWBAXmXNbAJAEYM5JU M1SbxClaOg4elTWXOhC7ubwS9geg/lKrrkZ5zf670DL6a9BjNM8vFQIH5aLdkgqQ qRNVoW6juKB+u9vwQTDDTOxFAWN/5gYUd/D8ZYp82/lsmoATYrPbbVmucXTLJsKA uBiOzMcVhWbVWskqKoIyexeNhgI3loic8oeDYCNtf9l5uGjWFgu6JA== =1ZQA -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
