Apple Event: May 7th at 7 am PT
I have just installed the update server app 4.0.3
When it installed all my users were missing, and i am no longer able to join the server on a client computer.
I have rebuilt my DNS and restarted all my services.
I am running a MacMini (10.10.2) server with various mac clients
When i try to join it using server.????.org.uk i get
Host not found
(9007)
When i try to join it using the server IP address i get
Connection failed to the directory server.
(2100)
Any ideas?
Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
1. The OD master must have a static IP address on the local network, not a dynamic address. It must not be connected to the same network with more than one interface; e.g., Ethernet and Wi-Fi.
2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
3. The primary DNS server used by the server must be itself, unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
4. If you have accounts with network home directories, make sure the URL's are correct in the user settings. A return status of 45 from the authorizationhost daemon in the log may mean that the URL for mounting the home directory was not updated after a change in the hostname.
5. Only if you're still running Mavericks server, follow these instructions to rebuild the Kerberos configuration on the server.
6. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases. Otherwise delete all certificates and create new ones.
7. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
8. Reboot the master and the clients.
9. Don't log in to the server with a network user's account.
10. Disable any internal firewalls in use, including third-party "security" software.
11. If you've created any replica servers, delete them.
12. If OD has only recently stopped working when it was working before, you may be able to restore it from the automatic backup in /var/db/backups, or from a Time Machine snapshot of that backup.
13. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.
If you get this far without solving the problem, then you'll need to examine the logs in the Open Directory section of the log list in the Server app, and also the system log on the clients.
Could there be a DNS problem? Can you ping the domain name and get an answer from the server (assuming you're not running in stealth mode)? The clients you are trying to bind to the server, what DNS are they using? Are they using the DNS in the OD server or some other? When you say that you have rebuilt the DNS does that mean you have rebuilt both the DNS records in the OD server and checked any other DNS used by the clients to find the OD server, both have to be in order? Do you miss a reverse lookup record for the server?
This has been helpful, but not solved my problem.
The Open Directory in the server app keeps switching its self off, and it won't allow me to assign a certificate to it.
Help! 🙂
Logs?
I turned OD on and it switched its self off, hopefully the system log will show that
Thanks for your help
Feb 27 07:01:59 server.thenashes.org.uk collabd[82053]: [main.m:366 75c7c300 +0ms] Configured to exit after about 360 seconds idle
Feb 27 07:01:59 server.thenashes.org.uk collabpp[82072]: Failed to obtain sandbox extension for path=/dev/null/Library/Caches/collabpp. Errno:20
Feb 27 07:02:00 --- last message repeated 1 time ---
Feb 27 07:02:00 server.thenashes.org.uk slapd[82092]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:00 server com.apple.xpc.launchd[1] (org.openldap.slapd[82092]): Service exited with abnormal code: 1
Feb 27 07:02:00 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:06 server.thenashes.org.uk xscertd-helper[82094]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:06 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82094]): Service exited with abnormal code: 1
Feb 27 07:02:06 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:10 server.thenashes.org.uk slapd[82099]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:10 server com.apple.xpc.launchd[1] (org.openldap.slapd[82099]): Service exited with abnormal code: 1
Feb 27 07:02:10 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:16 server.thenashes.org.uk xscertd-helper[82102]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:16 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82102]): Service exited with abnormal code: 1
Feb 27 07:02:16 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:20 server.thenashes.org.uk slapd[82106]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:20 server com.apple.xpc.launchd[1] (org.openldap.slapd[82106]): Service exited with abnormal code: 1
Feb 27 07:02:20 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:26 server.thenashes.org.uk xscertd-helper[82108]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:26 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82108]): Service exited with abnormal code: 1
Feb 27 07:02:26 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:30 server.thenashes.org.uk slapd[82113]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:30 server com.apple.xpc.launchd[1] (org.openldap.slapd[82113]): Service exited with abnormal code: 1
Feb 27 07:02:30 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:36 server.thenashes.org.uk xscertd-helper[82116]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:36 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82116]): Service exited with abnormal code: 1
Feb 27 07:02:36 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:40 server.thenashes.org.uk slapd[82120]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:40 server com.apple.xpc.launchd[1] (org.openldap.slapd[82120]): Service exited with abnormal code: 1
Feb 27 07:02:40 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:46 server.thenashes.org.uk xscertd-helper[82124]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:46 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82124]): Service exited with abnormal code: 1
Feb 27 07:02:46 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:50 server.thenashes.org.uk slapd[82130]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:02:50 server com.apple.xpc.launchd[1] (org.openldap.slapd[82130]): Service exited with abnormal code: 1
Feb 27 07:02:50 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:02:56 server.thenashes.org.uk xscertd-helper[82131]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:02:56 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82131]): Service exited with abnormal code: 1
Feb 27 07:02:56 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:03:00 server com.apple.xpc.launchd[1] (org.openldap.slapd[82138]): Service exited with abnormal code: 1
Feb 27 07:03:00 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:03:06 server.thenashes.org.uk xscertd-helper[82142]: ldap_search_ext_s returned -1 - Can't contact LDAP server when searching for bdb suffix, exiting
Feb 27 07:03:06 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper[82142]): Service exited with abnormal code: 1
Feb 27 07:03:06 server com.apple.xpc.launchd[1] (com.apple.xscertd-helper): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
Feb 27 07:03:11 server.thenashes.org.uk slapd[82153]: unable to open LA file: /usr/lib/sasl2/openldap//libcrammd5.la
Feb 27 07:03:11 server com.apple.xpc.launchd[1] (org.openldap.slapd[82153]): Service exited with abnormal code: 1
Feb 27 07:03:11 server com.apple.xpc.launchd[1] (org.openldap.slapd): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
What do you get from this:
sudo /usr/libexec/slapd -Tt
nothing 😟
Did you take Step 13?
TThat's fixed it but I have already lost all my users so can't export them, will have to rebuild it 😟
I can't do Step 13, the OD doesn't start and so there's nothing in the view.
I ran sudo db_recover -h /var/db/openldap/openldap-data/ but didn't fix it.
I ran sudo /usr/libexec/slapd -Tt and got:
5540473b bdb(dc=myDomain,dc=com): file id2entry.bdb has LSN 1/1524604, past end of log at 1/642307
5540473b bdb(dc=myDomain,dc=com): Commonly caused by moving a database from one database environment
5540473b bdb(dc=myDomain,dc=com): to another without clearing the database LSNs, or by removing all of
5540473b bdb(dc=myDomain,dc=com): the log files from a database environment
5540473b bdb(dc=myDomain,dc=com): /var/db/openldap/openldap-data/id2entry.bdb: unexpected file type or format
5540473b bdb_db_open: database "dc=myDomain,dc=com": db_open(/var/db/openldap/openldap-data/id2entry.bdb) failed: Invalid argument (22).
5540473b backend_startup_one (type=bdb, suffix="dc=myDomain,dc=com"): bi_db_open failed! (22)
slap_startup failed (test would succeed using the -u switch)
How do I clear the DB?
This worked for me: Re: Mac OS Server Open Directory Will Not Turn On However Mail in Server doesn't start, it stalls at 'Downloading virus definitions ... '
Server 4.0.3 unable to log in
