* Brand new Xserve running a freshly installed OS (10.5.7) with all the latest security patches
* Pointed to internal NTP server
* DNS looks good and changeip -checkhostname comes back clean before bind.
* I do not have any services configured or turned on at this point yet
Hello,
I have run into a problem when building a new 10.5.7 server in which after binding to Active Directory, the console log continuously shows the following messages about slapd:
[i]com.apple.launchd[1] (org.openldap.slapd[283]): Exited with exit code: 1
com.apple.launchd[1] (org.openldap.slapd): Throttling respawn: Will start in 10 seconds[/i]
I had thought that slapd wasn’t necessary for Active Directory, but I may be wrong. I tried unbinding from AD and the messages still continued even after a reboot. I came across this article that seems to have stopped these error messages. I’m not sure if this is a solution or not to my problem… or if there is a better approach.
http://blog.macadmincorner.com/slapd-error-in-systemlog/
If I follow the instructions from the above article and run slapd -Tt again, it says that the configuration file is not optimized and may cause issues. I rebuilt the server to investigate a bit more on my own, and the /etc/openldap/slapd.conf file is not created after the install and a slapd -Tt comes back stating the same. I however do not receive the errors in the console log until I bind again to AD.
AppleCare told me that to open a ticket with an Engineer would cost over $600. I’m not sure why as this may be a bug on their side of things. I have sucessfully bound clients and test servers to AD before without this happening, nothing in our AD environment has changed recently that I’m aware of.
Is there any difference in binding to AD using the Directory Util versus Server Admin? I would assume the best way is through Directory Util as you have a bit more control over the bind and it’s options.
Does anyone have any suggestions or insight? Thank you for your help.
-Ken
.
.
Comments are closed