Hi, It seems we've hit the same bug here: we had to reboot our server twice, and upon restart, slapd went into just the same sched_yield() loop with the same backtrace. Running db4.2_recover worked fine to correct things while LD_ASSUME_KERNEL=2.4 didn't help. Our system is really far from being overloaded so I don't think we hit the max_lockers limit. If you want, I kept a copy of the database, both erroneous and corrected by db4.2_recover. Julien, there's nothing *that* much sensitive in them, maybe we can privately post an url holding them ?
Regards, Samuel Thibault -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
