20091017 installing the 389 directory server - plembo/onemoretech GitHub Wiki

title: Installing the 389 Directory Server link: https://onemoretech.wordpress.com/2009/10/17/installing-the-389-directory-server/ author: lembobro description: post_id: 226 created: 2009/10/17 21:07:13 created_gmt: 2009/10/17 21:07:13 comment_status: open post_name: installing-the-389-directory-server status: publish post_type: post

Installing the 389 Directory Server

It’s been quite awhile since I’ve taken a look at the Fedora Directory Server. By the time of my last review the process of installing the latest version it to a RHEL/CentOS server had become a bit complicated. With it’s re-branding as the 389 Directory Server the time had come to give it another try.

The download page is here, with pointers to other documentation, which is all very good. The Release Notes have more info on changes over time. As usual, kudos to Rich Megginson for getting it done once again.

Test bed was my home CentOS 5.3 workstation with a dual core Pentium D and 4 Gb RAM (not that is can actually use more than 3 Gb even when running a 64-bit O/S… and then Dell wonders why I won’t buy any more computers from them!).

1. Set up the yum repos for a RHEL 5 system:

wget -O - http://port389.org/sources/idmcommon.repo | sed -e 's/$releasever/6/g;' > /etc/yum.repos.d/idmcommon.repo

wget -O - http://port389.org/sources/dirsrv.repo | sed -e 's/$releasever/6/g;' > /etc/yum.repos.d/dirsrv.repo

rpm --import 'http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA7B02652'

2. Do a yum install for the 389 directory packages:

yum install 389-ds --enablerepo=dirsrv-testing --enablerepo=idmcommon-testing

3. Packages that will install:

 Package                Arch    Version                Repository          Size
================================================================================
Installing:
 389-ds                 noarch  1.1.3-4.el5            dirsrv-noarch      8.6 k
Installing for dependencies:
 389-admin              i386    1.1.9-1.el5            dirsrv-testing     373 k
 389-admin-console      noarch  1.1.4-1.el5            dirsrv-noarch      201 k
 389-admin-console-doc  noarch  1.1.4-1.el5            dirsrv-noarch       39 k
 389-adminutil          i386    1.1.8-3.el5            dirsrv              68 k
 389-console            noarch  1.1.3-4.el5            idmcommon-testing   72 k
 389-ds-base            i386    1.2.3-1.el5            dirsrv-testing     1.7 M
 389-ds-console         noarch  1.2.0-4.el5            dirsrv-noarch      1.4 M
 389-ds-console-doc     noarch  1.2.0-4.el5            dirsrv-noarch       53 k
 389-dsgw               i386    1.1.4-1.el5            dirsrv             1.1 M
 cyrus-sasl-gssapi      i386    2.1.22-4               base                28 k
 idm-console-framework  noarch  1.1.3-9.el5.centos.2   extras             1.0 M
 jss                    i386    4.2.5-1.el5.centos.1   extras             681 k
 ldapjdk                i386    4.18-2jpp.3.el5        base               782 k
 lm_sensors             i386    2.10.7-4.el5           base               513 k
 mod_nss                i386    1.0.3-7.el5_3.1        updates             81 k
 mozldap                i386    6.0.5-1.el5            base               132 k
 mozldap-tools          i386    6.0.5-1.el5            base               139 k
 perl-Mozilla-LDAP      i386    1.5.2-4.el5            base               181 k
 svrcore                i386    4.0.4-3.el5            base                14 k
	
Transaction Summary
================================================================================
Install     20 Package(s)
Update       0 Package(s)
Remove       0 Package(s)

(the above listing is mostly for my own recordkeeping purposes: if this thing goes bad I need to know what packages to remove from the system)

The various pieces install to the usual standard places (at least for a Red Hat box). Here are a few new paths you’ll find:

/etc/dirsrv /usr/share/dirsrv /usr/lib/dirsrv /var/lib/dirsrv (this is where you directory data lives)

4. Configure the admin and directory servers:

Once you’re done with the above, the next step is to run the config program program, /usr/sbin/setup-ds-admin.pl for a “Typical” install. The result will be directory and admin servers up, running and ready to rock. The 389console app replaces the former startconsole gui for administration, although it looks and behaves just like its predecessor (OK, it is a bit faster and more stable).

389console