ユーザ用ツール

サイト用ツール


サイドバー

Top

検索タグ

変更履歴

メニュー


linux:389-directory-server

389 Directory Server

 このディレクトリサーバーは以前に Fedora Directory Server(FDS) と呼ばれていましたが、2009年5月に 389 Directory Server に名称変更されました。
 日本語の文献を探す場合は、Fedora Directory Server(FDS) を検索する方が良いかもしれません。

 以降では、Fedora 19 の環境に 389 Directory Server を導入してみる。

389-ds のインストール

 以下のコマンドを実行して 389 Directory Server と関連パッケージを導入する。

$ sudo yum install 389-ds

389-ds サービス実行ユーザーの作成

 Fedoraの一般ユーザーのuid/gidは1000から開始するので、以下のファイルを眺めて決める。

$ cat /etc/login.defs

 参考: 3. Fedora の変更点 - システム管理者向け

 サービス実行ユーザーの作成

$ sudo groupadd -g 10000 ldap
$ sudo useradd -u 10000 -g ldap ldap

Linuxのチューニング

 以下の資料に習って設定をすませておく。
389 Directory Server (Open Source LDAP)

 チューニングをすませておかないとセットアップ中に警告される事がある。

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
environment.

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

NOTICE : System is x86_64-unknown-linux3.11.1-200.fc19.x86_64 (1 processor).

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.

ファイルディスクリプタ上限の変更

最終行に設定を追記する。

$ sudo vi /etc/security/limits.conf 
*               soft    nofile          8192
*               hard    nofile          8192
$ sudo vi /etc/profile 
ulimit -n 8192

ネットワークパラメータの変更

最終行に設定を追記する。

$ sudo vi /etc/sysctl.conf
net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.tcp_keepalive_time = 300

チューニングの反映

$ sudo reboot

初期設定のバックアップ

 初期状態に戻すことを可能にするために、以下のコマンドを実行してディレクトリのバックアップを行う。

$ sudo cp -rf /etc/dirsrv /etc/dirsrv.org

setup-ds-admin.pl の実行

 ディレクトリサーバーをセットアップするために、以下のコマンドを実行する。

$ sudo setup-ds-admin.pl
==============================================================================
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

Would you like to continue with set up? [yes]:

セットアップを続行する場合は、そのまま Enter キーを入力する。

==============================================================================
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
environment.

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

NOTICE : System is x86_64-unknown-linux3.11.1-200.fc19.x86_64 (1 processor).

Would you like to continue? [yes]:

通知のみなので、そのまま Enter キーを入力して続行する。

==============================================================================
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.

Choose a setup type [2]:

セットアップタイプはデフォルトのまま Enter キーを入力して続行する。

==============================================================================
Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: eros.example.com.

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:

    General.FullMachineName=your.hostname.domain.name

Computer name [green-ds.fireball.local]:

コンピュータ名はデフォルトのまま Enter キーを入力して続行する。

==============================================================================
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.

System User [nobody]: ldap
System Group [nobody]: ldap

サービスを特定のユーザー/グループの権限で実行するために、予め ldapユーザーを作成しておき、それをここで指定する。

==============================================================================
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
<hostname>.<domainname>(e.g. hostname.example.com), 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.

Do you want to register this software with an existing
configuration directory server? [no]: 

既存のディレクトリサーバーが存在しない場合は、Enter キーを入力して続行する。

==============================================================================
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.

Configuration directory server
administrator ID [admin]:
Password:
Password (confirm):

ディレクトリサーバーの管理者IDとパスワードを設定する。
管理者IDはデフォルトのまま Enter キーを入力し、任意のパスワードを入力する。

==============================================================================
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.

Administration Domain [fireball.local]: 

管理ドメインはデフォルトのまま Enter キーを入力して続行する。

==============================================================================
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.

Directory server network port [389]:

ディレクトリサーバーのポート番号もデフォルトのまま Enter キーを入力して続行する。

==============================================================================
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.

Directory server identifier [green-ds]: 

ディレクトリサーバーの識別子もデフォルトのまま Enter キーを入力して続行する。

==============================================================================
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 example.com,
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.

Suffix [dc=fireball, dc=local]:

ディレクトリサーバーのサフィックスもデフォルトのまま Enter キーを入力して続行する。

==============================================================================
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.

Directory Manager DN [cn=Directory Manager]: 
Password: 
Password (confirm):

ディレクトリマネージャのDN(識別名)とパスワードを設定する。
DNはデフォルトのまま Enter キーを入力し、任意のパスワードを入力する。

==============================================================================
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
restricted.

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.

Administration port [9830]:

管理サーバーのポート番号もデフォルトのまま Enter キーを入力して続行する。

==============================================================================
The interactive phase is complete.  The script will now set up your
servers.  Enter No or go Back if you want to change something.

Are you ready to set up your servers? [yes]:

問い合わせに対して Enter キーを入力して続行する。

Creating directory server . . .
Your new DS instance 'green-nas' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
Starting admin server . . .
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setupwakfkC.log'

ディレクトリサーバーの作成、管理サーバーの構成が行われて、サービスが起動される。

サービス自動起動設定

$ sudo systemctl enable dirsrv-admin.service
$ sudo systemctl enable dirsrv@green-ds.service

firewall設定

$ sudo firewall-cmd --permanent --add-service=ldap
$ sudo firewall-cmd --permanent --add-service=ldaps
$ sudo firewall-cmd --permanent --add-port=9830/tcp
$ sudo firewall-cmd --reload
$ sudo firewall-cmd --list-services
ipp-client mdns ldaps dhcpv6-client ldap
$ sudo firewall-cmd --list-ports
9830/tcp

ディレクトリサーバーと管理サーバーの起動確認

 以下のコマンドを実行してプロセスが起動していることを確認する。

$ ps aux | grep ldap
ldap      1104  0.1  1.0 1090784 20536 ?       Sl   16:03   0:07 /usr/sbin/ns-slapd -D /etc/dirsrv/
slapd-green-ds -i /var/run/dirsrv/slapd-green-ds.pid -w /var/run/dirsrv/slapd-green-nas.startpid
ldap      1190  0.0  0.3 772224  6428 ?        Sl   16:04   0:00 /usr/sbin/httpd -k start -f
 /etc/dirsrv/admin-serv/httpd.conf
プロセスの説明
ns-slapd 389 Directory Server のプロセス
httpd.worker -k start -f /etc/dirsrv/admin-serv/httpd.conf 管理サーバー用HTTPデーモン


 プロセスが正常に起動していない場合は、以下のパスに存在するログファイルの内容を確認して対処を行う。

/var/log/dirsrv/admin-serv -> 管理サーバーログ
/var/log/dirsrv/slapd-xxxx(ホスト名) -> ディレクトリサーバーのログ

Directory Server インスタンスの削除

$ sudo remove-ds.pl -i slapd-instancename

トラブルシューティング

dirsrv-admin.service が起動しない

ステータスを確認すると、以下のエラーが出力されている。

$ sudo systemctl status dirsrv-admin.service
PID file /var/run/dirsrv/admin-serv.pid not readable (yet?) after start.
dirsrv-admin.service never wrote its PID file. Failing.
Failed to start 389 Administration Server..
Unit dirsrv-admin.service entered failed state.

#47429 (dirsrv fails to start due to incorrect /var/run/lock lines in tmpfiles.d) – 389 Projectのバグの可能があるので、以下のファイルを確認する。

$ cat /etc/tmpfiles.d/dirsrv-blue-ds.conf 
d /var/dirsrv 0770 ldap ldap
d /var/lock/dirsrv 0770 ldap ldap
d /var/lock/dirsrv/slapd-blue-ds 0770 ldap ldap

/var/run/dirsrv の記載が存在しない場合は追記する。

$ sudo vi /etc/tmpfiles.d/dirsrv-blue-ds.conf 
d /var/dirsrv 0770 ldap ldap
d /var/run/dirsrv 0770 ldap ldap <- 追記
d /var/lock/dirsrv 0770 ldap ldap
d /var/lock/dirsrv/slapd-blue-ds 0770 ldap ldap

再起動する。

$ sudo reboot

参考文献

linux/389-directory-server.txt · 最終更新: 2019/05/18 02:23 (外部編集)