Around 8 days ago our master server started to show signs of corruption, and, sure enough, I had lost the ability to authenticate and make changes to the database. Luckily, at this point, the database was still functioning. So I handed off the the replica, and took the master offline to sort things out.
My normal routine when this happens(and it seems to, at least once a year) is to simply replace the /var/db folder with the backup -- while I admit this is a rather ugly method, it normally works. This time, it didn't. I presume the backup was already poisoned. Many days of hair pulling, googling, and poking around left me no better off -- i'd really like to avoid a fresh install.
As a last resort, I nuked(read:renamed/moved) the /var/db folder, inhope of invoking some kind of rebuild mechanism. This has worked to the extent that i was able to re-enter all the configuration data, however the ldap now displays a -14002.
A terrible hackjob, I know -- but i ran into tremendous frustration tracking down troubleshooting information for ldap(the Apple Mac OSX Server discussion fora seem to have a poor signal:noise ratio).
And so, dear readers, my question is -- how does one force a complete rebuild of the LDAP database under Mac OSX Server 10.3.5? Is a clean install now my only option?
Many thanks for your time,
Mikir.