I'm still new to OS X server and am slowly making my way toward
getting things setup. What I am trying to do is first Integrate AD/
OD and once that is setup, create an OD replica to ensure stability.
I have the AD/OD setup working fine. I used the various guides and
it seems to work well. I've configured what I think is an OK setup
on the OD master. Now I am trying to setup the OD replica.
Unfortunately it doesn't seem to work. xserve2 has not been anything
but a standalone server. I did join it to AD and at that point its
role became "Connected to a directory system". I found one thread
at http://www.afp548.com/forum/viewtopic.php?showtopic=9384 but I
want to understand and don't want to just start blindly following
instructions found through google.
So my question is this: Am I on the right track to OD master/
replica, and if so, how should I go about troubleshooting this?
(remember I'm green)
Dec 18 13:00:16 xserve1 slapd[12632]: slapd shutdown: waiting for 0
threads to terminate\n
Dec 18 13:00:16 xserve1 slapd[12632]:
bdb(dc=xserve1,dc=hadw,dc=com): Locker still has locks\n
Dec 18 13:00:16 xserve1 slapd[12632]: bdb_locker_id_free: 7 err
Invalid argument(22)\n
This one looks somewhat weird .. the bdb is the database that is used
to store the LDAP data. It looks like you can't cleanly shut down the
database. Which kind of hits you later on.
These warnings are normal. It's just that Apple didn't index these
entries. If you get too many timeouts you can try and add them to /etc/
openldap/slapd_macosxserver.conf (towards the end of the file are the
pre-defined indexes). Don't forget to shutdown the ldap Database and
do a 'slapindex' afterwards.
Here is where your error happens. Try to execute the command ' /usr/
sbin/slapcat -l /var/db/openldap/openldap-data/backup.ldif' on your
Master server and checkl for error messages. That might give you some
more hints.
At least it looks your 'future' OD replica is not the cause for things.
I think your problem might be related to the 'bdb_locker_id_free'
error. Do you see that every time?
If so it might be worth to do Archive, Demote, re-promote and Restore
your OD master again. This should give you a clean database.