Aaron, Quanah,
Thanks for your input. It turned out to be a bdb issue. However, I
was under the assumption that OpenLDAP v2.3.x automatically ran
db_recover by putting it in /etc/init.d/ldap2.3. When I ran slapcat2.3
to see if the DB was okay (I know that there are other ways, but
slapcat2.3 was the quickest thing since I thought that db_recover had
already been run), it seemed to work and then it told me that it was
trying to fix the database because it wasn't in a good state. CPU
Utilization went up to 100% and stracing it showed that it was in an
infinite loop of sched_yield() = 0 as well