LDAP does not start after suffix is created
After creating the secAuthority=Default suffix Security Directory Server does not start. The following steps are required to prepare an LDAP server for use with ISAM. These steps must be completed before we configure IBM Security Verify Access:
- Create the secAuthority=Default suffix.
- Stop and restart the Security Directory Server to enable the server to recognize the newly created suffix
When command-line installation is used, these steps must be completed manually.
If the user attempts to create the secAuthority=Default suffix and restart Security Directory Server before we apply the schema modifications required by ISAM, Security Directory Server fails to restart.
When the server fails to restart it logs an error message to the slapd.errors file. This message indicates the secAuthority attribute is not defined. The slapd.errors file is in the /tmp directory on AIX, Linux, and Solaris operating systems and in the ldap_install_dir\tmp directory on Windows operating systems, where ldap_install_dir is the directory where Security Directory Server was installed.
Parent topic: LDAP common problems