Back to the main page

The 389 Directory Server Installation


The 389 Directory Server is basically LDAP server. This example is for Oracle/RedHat 7.
If you want firewall, have open ports 389, 636 (ldap, ldaps) and 9830 (for admin server).

Install 389 Directory Server

Create a LDAP user and group.
# id ldapadmin
uid=1813(ldapadmin) gid=1813(ldapadmin) groups=1813(ldapadmin)

Have repo "epel", it's needed for 389 Administration Server and Mgmt Console.
# cat epel.repo
name=Extra Packages for Enterprise Linux 7 - $basearch

name=Extra Packages for Enterprise Linux 7 - $basearch - Debug

Some RPMs may need this repo ...
name=Oracle Linux $releasever Latest ($basearch)

... like
#  yum info 389-ds-base 
Loaded plugins: ulninfo
Installed Packages
Name        : 389-ds-base
Arch        : x86_64
Version     :
Release     : 30.el7_2
Size        : 5.2 M
Repo        : installed
From repo   : ol7_latest
Summary     : 389 Directory Server (base)
URL         :
License     : GPLv3+
Description : 389 Directory Server is an LDAPv3 compliant server.  The base package includes
            : the LDAP server and command line utilities for server administration.

Start install with command, and try fixing any dependency issues with manual additional rpm install.
# yum install 389-ds-base openldap-clients

The 389-ds configuration

Just run the file /sbin/
# file /sbin/
/sbin/ Perl script, ASCII text executable

Here is what happens ...
[16/05/05:23:57:09] - [Setup] Info This program will set up the 389 Directory and Administration Servers.

It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
  - Press "Enter" to choose the default and go to the next screen
  - Type "Control-B" then "Enter" to go back to the previous screen
  - Type "Control-C" to cancel the setup program

[16/05/05:23:57:09] - [Setup] Info Would you like to continue with set up?
[16/05/05:23:57:11] - [Setup] Info yes
[16/05/05:23:57:11] - [Setup] Info Your system has been scanned for potential problems, missing patches,
etc.  The following output is a report of the items found that need to
be addressed before running this software in a production

389 Directory Server system tuning analysis version 23-FEBRUARY-2012.

NOTICE : System is x86_64-unknown-linux3.8.13-118.4.1.el7uek.x86_64 (2 processors).

NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes).  This may cause temporary server congestion from lost
client connections.

WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.

WARNING  : The warning messages above should be reviewed before proceeding.

[16/05/05:23:57:11] - [Setup] Info Would you like to continue?
[16/05/05:23:57:14] - [Setup] Info yes
[16/05/05:23:57:14] - [Setup] Info Choose a setup type:

   1. Express
       Allows you to quickly set up the servers using the most
       common options and pre-defined defaults. Useful for quick
       evaluation of the products.

   2. Typical
       Allows you to specify common defaults and options.

   3. Custom
       Allows you to specify more advanced options. This is
       recommended for experienced server administrators only.

To accept the default shown in brackets, press the Enter key.

[16/05/05:23:57:14] - [Setup] Info Choose a setup type
[16/05/05:23:57:15] - [Setup] Info 2
[16/05/05:23:57:15] - [Setup] Info Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form

To accept the default shown in brackets, press the Enter key.

Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly.  If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:

[16/05/05:23:57:15] - [Setup] Info Computer name
[16/05/05:23:57:16] - [Setup] Info
[16/05/05:23:57:16] - [Setup] Info The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user).  The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.

If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.

[16/05/05:23:57:16] - [Setup] Info System User
[16/05/05:23:57:18] - [Setup] Info ldapadmin
[16/05/05:23:57:18] - [Setup] Info System Group
[16/05/05:23:57:20] - [Setup] Info ldapadmin
[16/05/05:23:57:20] - [Setup] Info Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers.  If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server.  To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
.(e.g., the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL).  If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).

If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.

[16/05/05:23:57:20] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[16/05/05:23:57:22] - [Setup] Info no
[16/05/05:23:57:22] - [Setup] Info Please enter the administrator ID for the configuration directory
server.  This is the ID typically used to log in to the console.  You
will also be prompted for the password.

[16/05/05:23:57:22] - [Setup] Info Configuration directory server
administrator ID
[16/05/05:23:57:23] - [Setup] Info admin
[16/05/05:23:57:23] - [Setup] Info Password
[16/05/05:23:57:26] - [Setup] Info Password (confirm)
[16/05/05:23:57:29] - [Setup] Info The information stored in the configuration directory server can be
separated into different Administration Domains.  If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.

If you are not using administrative domains, press Enter to select the
default.  Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.

[16/05/05:23:57:29] - [Setup] Info Administration Domain
[16/05/05:23:57:34] - [Setup] Info
[16/05/05:23:57:34] - [Setup] Info The standard directory server network port number is 389.  However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.

[16/05/05:23:57:34] - [Setup] Info Directory server network port
[16/05/05:23:57:35] - [Setup] Info 389
[16/05/05:23:57:35] - [Setup] Info Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.

[16/05/05:23:57:35] - [Setup] Info Directory server identifier
[16/05/05:23:57:39] - [Setup] Info ldap01
[16/05/05:23:57:39] - [Setup] Info The suffix is the root of your directory tree.  The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.

[16/05/05:23:57:39] - [Setup] Info Suffix
[16/05/05:23:57:44] - [Setup] Info dc=company, dc=com
[16/05/05:23:57:44] - [Setup] Info Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user.  The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.

[16/05/05:23:57:44] - [Setup] Info Directory Manager DN
[16/05/05:23:57:46] - [Setup] Info cn=Directory Manager
[16/05/05:23:57:46] - [Setup] Info Password
[16/05/05:23:57:49] - [Setup] Info Password (confirm)
[16/05/05:23:57:52] - [Setup] Info The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is

Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.

[16/05/05:23:57:52] - [Setup] Info Administration port
[16/05/05:23:57:54] - [Setup] Info 9830
[16/05/05:23:57:54] - [Setup] Info The interactive phase is complete.  The script will now set up your
servers.  Enter No or go Back if you want to change something.

[16/05/05:23:57:54] - [Setup] Info Are you ready to set up your servers?
[16/05/05:23:57:56] - [Setup] Info yes
[16/05/05:23:57:56] - [Setup] Info Creating directory server . . .
[16/05/05:23:58:00] - [Setup] Info Your new DS instance 'ca-ldap04' was successfully created.
[16/05/05:23:58:00] - [Setup] Info Creating the configuration directory server . . .
[16/05/05:23:58:01] - [Setup] Info Beginning Admin Server creation . . .
[16/05/05:23:58:01] - [Setup] Info Creating Admin Server files and directories . . .
[16/05/05:23:58:01] - [Setup] Info Updating adm.conf . . .
[16/05/05:23:58:01] - [Setup] Info Updating admpw . . .
[16/05/05:23:58:01] - [Setup] Info Registering admin server with the configuration directory server . . .
[16/05/05:23:58:01] - [Setup] Info Updating adm.conf with information from configuration directory server . . .
[16/05/05:23:58:01] - [Setup] Info Updating the configuration for the httpd engine . . .
[16/05/05:23:58:01] - [Setup] Info Starting admin server . . .
[16/05/05:23:58:01] - [Setup] Info The admin server was successfully started.
[16/05/05:23:58:01] - [Setup] Info Admin server was successfully created, configured, and started.
[16/05/05:23:58:01] - [Setup] Success Exiting . . .

Service management

Enable and start services: Admin Server is HTTP based admin engine used by Directory Server to run web based console.
[root@ldap01 ~]#  systemctl status - 389 Directory Server
   Loaded: loaded (/usr/lib/systemd/system/; enabled; vendor preset: disabled)
   Active: active since Thu 2016-05-19 00:29:47 PDT; 1 months 12 days ago

May 19 00:29:47 systemd[1]: Reached target 389 Directory Server.
May 19 00:29:47 systemd[1]: Starting 389 Directory Server.

[root@ldap01 ~]#  systemctl status dirsrv-admin 
 dirsrv-admin.service - 389 Administration Server.
   Loaded: loaded (/usr/lib/systemd/system/dirsrv-admin.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2016-05-18 09:10:07 PDT; 1 months 13 days ago
  Process: 562 ExecStart=/usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf (code=exited, status=0/SUCCESS)
 Main PID: 581 (httpd)
   CGroup: /system.slice/dirsrv-admin.service
           |-581 /usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf
           |-582 /usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf
           |-583 /usr/sbin/httpd -k start -f /etc/dirsrv/admin-serv/httpd.conf

May 18 09:10:06 systemd[1]: Starting 389 Administration Server....
May 18 09:10:07 systemd[1]: PID file /var/run/dirsrv/ not readable (yet?) after start.
May 18 09:10:07 systemd[1]: Started 389 Administration Server..

And login via GUI console.

Back to the main page