--On Monday, April 16, 2007 6:54 PM +0200 Gyuris Szabolcs
<[EMAIL PROTECTED]> wrote:
Quanah Gibson-Mount wrote:
--On Monday, April 16, 2007 9:57 AM +0200 Gyuris Szabolcs
<[EMAIL PROTECTED]> wrote:
Hi Quanah!
I set the checkpoint to "2048 10".
But the shutdown wasn't the problem. The problem is that after variable
time slapd won't answer to any questions. The number of threads are
growing and the system load too.
Ah, okay. I misread it as a being a problem with slapd at shutdown time.
Sorry it's my poor English :(
You are doing quite well. :)
First, do you have a DB_CONFIG file in /var/lib/ldap that has been
-- DB_CONFIG --
set_cachesize 0 2097152 0
set_lk_max_objects 1500
set_lk_max_locks 1500
set_lk_max_lockers 1500
-- DB_CONFIG --
It's the debian default.
Okay, so that is a 2 MB cache, which is sufficient, since your id2entry is
only 772K.
properly tuned for your database? If not, if you could send the output
of `cat /var/lib/ldap/DB_CONFIG` and `du -h id2entry.bdb`
-- DU --
772K id2entry.bdb
-- DU --
Second, how many CPU's does your system have?
1 CPU and it's a vmware-server guest OS.
Okay, definitely add "threads 8" to the global section of slapd.conf. The
default number of threads for slapd is 16, which is substantially past the
mark for most systems, and has a rather negative impact.
Third, what is the total amount of RAM on your system?
cat /proc/meminfo:
MemTotal: 127032 kB
Well, 128MB should be okay if slapd's BDB cache is only 2MB.
Another setting you should likely set would be the cachesize, in the
database specific area of slapd.conf. Given that your total number of
entries is small, I'd set it to that number (for example, "cachesize 1000"
for a 1000 entry DB).
If things freeze again, can you please get the output of:
db_stat -h /var/lib/ldap -c
Thanks!
--Quanah
--
Quanah Gibson-Mount
Senior Systems Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
