Open Directory won't start after crash no logins

Question

Server was crashed due to work in the room. OD will not start. I've tried every fix I can find, but the main problem is that this command will not work:
sudo launchctl unload /System/Library/LaunchDaemons/org.openldap.slapd.plist
I also have time machine backups but which files should I replace? Thanks

Answer 1

Hi,
First thing to check is that DNS is set up correctly.
in Terminal, type:
$ sudo changeip -checkhostname
This should return your server IP address, current hostname and DNS hostname; the hostnames should be the same.
Finally it should issue a message that says:
The names match. There is nothing to change.
dirserv:success = “success”
if there is a mismatch here, you will need to fix in the Network tab of the Server app, and the DNS settings.
It could also be a problem with a remnant of a previous OD setup although you say that you are attempting to set it up, so not sure why there would be a remnant.
You can "clean out" the old LDAP info by issuing this command but it will wipe out your Open Directory databases on the machine you issue it on; you have been warned....
Doing this will then let Server app prompt you in the OD settings to 1. set up OD or 2. restore from an archive.
The command is:
$ sudo slapconfig -destroyldapserver
Finally , if you are having problems, turn on logging:
$ sudo slapconfig -enableslapdlog
this writes OD logs to /var/log/slapd.log
Hope that helps. I had that exact issue on a server that was hosting a replica and that stopped working after update of server.app .