![\"389\"](\"https:\/\/webhostinggeeks.com\/howto\/wp-content\/uploads\/2011\/03\/3891.png\" "\\"389\\"")
<\/p>\n<\/p>\n
This post will share with you on how to perform system tuning analysis, install and configure 389 Directory Server on linux CentOS 6.2 server. 389 Directory Server is an enterprise-class open source LDAP server for Linux. It is based on Fedora Directory Server. This post assumed that your CentOS server has been completely setup EPEL repository.<\/p>\n
Before start to configure the 389 Directory Server, it is better to adjust some performance and security settings. Follow the following steps to tuning the 389 Directory Server on CentOS 6.2.<\/p>\n
a) Decrease the time default value for tcp_keepalive_time connection. Edit the \/etc\/sysctl.conf file and add the following lines to the bottom of sysctl.conf.<\/p>\n
[root@centos62 ~]# vi \/etc\/sysctl.conf<\/pre>\n#Decrease the time default value for tcp_keepalive_time connection\nnet.ipv4.tcp_keepalive_time = 300<\/pre>\nb) Increase number of local system ports available by editing this parameter in the \/etc\/sysctl.conf file :<\/p>\n
[root@centos62 ~]# echo \"net.ipv4.ip_local_port_range = 1024 65000\" >> \/etc\/sysctl.conf<\/pre>\nShow changes :<\/p>\n
[root@centos62 ~]# cat \/etc\/sysctl.conf | grep net.ipv4.ip_local_port_range\nnet.ipv4.ip_local_port_range = 1024 65000<\/pre>\n1.2 Perform File Tuning :<\/h3>\n
a) Increase the file descriptors by running these commands:<\/p>\n
[root@centos62 ~]# echo \"64000\" > \/proc\/sys\/fs\/file-max<\/pre>\nShow changes :<\/p>\n
[root@centos62 ~]# cat \/proc\/sys\/fs\/file-max\n64000<\/pre>\nor
\nSimply run this command :<\/p>\n[root@centos62 ~]# echo \"fs.file-max = 64000\" >> \/etc\/sysctl.conf<\/pre>\nShow changes :<\/p>\n
[root@centos62 ~]# cat \/etc\/sysctl.conf | grep fs.file-max\nfs.file-max = 64000<\/pre>\nb) Edit \/etc\/profile as below :<\/p>\n
[root@centos62 ~]# echo \"ulimit -n 8192\" >> \/etc\/profile<\/pre>\nShow changes :<\/p>\n
[root@centos62 ~]# cat \/etc\/profile | grep ulimit\nulimit -n 8192<\/pre>\nc) Edit the file descriptors in \/etc\/security\/limits.conf. Add two parameter at the bottom of the configuration file :<\/p>\n
[root@centos62 ~]# vi \/etc\/security\/limits.conf<\/pre>\n# End of file\n* soft nofile 524288\n* hard nofile 524288<\/pre>\n1.3 Directory Server Tuning :<\/h3>\n
a) Edit \/etc\/sysconfig\/dirsrv and uncomment “ulimit -n 8192”<\/p>\n
[root@centos62 ~]# cat \/etc\/sysconfig\/dirsrv | grep ulimit<\/pre>\n# hard limits are raised, then use ulimit - uncomment\n# ulimit -n 8192<\/pre>\nEdit as below :<\/p>\n
[root@centos62 ~]# vi \/etc\/sysconfig\/dirsrv<\/pre>\n# In order to make more file descriptors available\n# to the directory server, first make sure the system\n# hard limits are raised, then use ulimit - uncomment\n# out the following line and change the value to the\n# desired value\nulimit -n 8192<\/pre>\n1.4 Sufficient Memory Assigned :<\/h3>\n
Make sure you have assign or upgrade the physical memory to at least 1024MB.<\/p>\n
2.0 Install 389 Directory Server on CentOS 6.2<\/h2>\n
This post will show you the quick steps to install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. This post assumed that your CentOS server has been completely installed with minimum packages and the hostname and FQDN also has been configured correctly. Please make sure that you have configured EPEL repository on your CentOS 6.2 server.<\/p>\n
Prerequisites :
\nHow to Setup Local Yum Repository from CD-ROM\/DVD-ROM image on CentOS 6.2<\/a>
\nHow to Install and Configure EPEL Repository on CentOS 6.2<\/a><\/p>\n2.1 Simply run this command to install 389 Directory Server on linux CentOS 6.2 server<\/h3>\n
[root@centos62 ~]# yum install 389-ds openldap-clients -y<\/pre>\nExamples :<\/p>\n
[root@centos62 ~]# yum install 389-ds openldap-clients -y\nLoaded plugins: fastestmirror\nLoading mirror speeds from cached hostfile\n * base: centos.ipserverone.com\n * epel: ftp.cuhk.edu.hk\n * extras: centos.ipserverone.com\n * updates: centos.ipserverone.com\nSetting up Install Process\nResolving Dependencies\n--> Running transaction check\n---> Package 389-ds.noarch 0:1.2.2-1.el6 will be installed\n--> Processing Dependency: 389-ds-console for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-ds-console-doc for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-admin-console-doc for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-ds-base for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-admin-console for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-admin for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: idm-console-framework for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-dsgw for package: 389-ds-1.2.2-1.el6.noarch\n--> Processing Dependency: 389-console for package: 389-ds-1.2.2-1.el6.noarch\n---> Package openldap-clients.i686 0:2.4.23-20.el6 will be installed\n--> Running transaction check\n---> Package 389-admin.i686 0:1.1.25-1.el6 will be installed\n--> Processing Dependency: perl-Mozilla-LDAP for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: nss-tools for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: policycoreutils-python for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: libicudata.so.42 for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: perl(Mozilla::LDAP::API) for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: perl(CGI) for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: libadminutil.so.0 for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: libadmsslutil.so.0 for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: perl(Mozilla::LDAP::Conn) for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: perl(Mozilla::LDAP::Utils) for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: libicui18n.so.42 for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: mod_nss for package: 389-admin-1.1.25-1.el6.i686\n--> Processing Dependency: libicuuc.so.42 for package: 389-admin-1.1.25-1.el6.i686\n---> Package 389-admin-console.noarch 0:1.1.8-1.el6 will be installed\n---> Package 389-admin-console-doc.noarch 0:1.1.8-1.el6 will be installed\n---> Package 389-console.noarch 0:1.1.7-1.el6 will be installed\n--> Processing Dependency: java >= 1:1.6.0 for package: 389-console-1.1.7-1.el6.noarch\n--> Processing Dependency: jpackage-utils for package: 389-console-1.1.7-1.el6.noarch\n---> Package 389-ds-base.i686 0:1.2.9.14-1.el6_2.2 will be installed\n--> Processing Dependency: 389-ds-base-libs = 1.2.9.14-1.el6_2.2 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: cyrus-sasl-md5 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libnetsnmpmibs.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: cyrus-sasl-gssapi for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libnetsnmphelpers.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libnetsnmpagent.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libnetsnmp.so.20 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libslapd.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n--> Processing Dependency: libsvrcore.so.0 for package: 389-ds-base-1.2.9.14-1.el6_2.2.i686\n---> Package 389-ds-console.noarch 0:1.2.6-1.el6 will be installed\n---> Package 389-ds-console-doc.noarch 0:1.2.6-1.el6 will be installed\n---> Package 389-dsgw.i686 0:1.1.7-2.el6 will be installed\n---> Package idm-console-framework.noarch 0:1.1.7-2.el6 will be installed\n--> Processing Dependency: jss >= 4.2 for package: idm-console-framework-1.1.7-2.el6.noarch\n--> Processing Dependency: ldapjdk for package: idm-console-framework-1.1.7-2.el6.noarch\n--> Running transaction check\n---> Package 389-adminutil.i686 0:1.1.14-2.el6 will be installed\n---> Package 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 will be installed\n---> Package cyrus-sasl-gssapi.i686 0:2.1.23-13.el6 will be installed\n---> Package cyrus-sasl-md5.i686 0:2.1.23-13.el6 will be installed\n---> Package java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 will be installed\n--> Processing Dependency: tzdata-java for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686\n--> Processing Dependency: rhino for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686\n--> Processing Dependency: libgif.so.4 for package: 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686\n---> Package jpackage-utils.noarch 0:1.7.5-3.12.el6 will be installed\n---> Package jss.i686 0:4.2.6-20.el6 will be installed\n---> Package ldapjdk.i686 0:4.18-6.el6 will be installed\n--> Processing Dependency: libgcj_bc.so.1 for package: ldapjdk-4.18-6.el6.i686\n--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686\n--> Processing Dependency: java-gcj-compat for package: ldapjdk-4.18-6.el6.i686\n---> Package libicu.i686 0:4.2.1-9.1.el6_2 will be installed\n---> Package mod_nss.i686 0:1.0.8-13.el6 will be installed\n---> Package net-snmp-libs.i686 1:5.5-37.el6_2.1 will be installed\n--> Processing Dependency: libsensors.so.4 for package: 1:net-snmp-libs-5.5-37.el6_2.1.i686\n---> Package nss-tools.i686 0:3.13.1-7.el6_2 will be installed\n--> Processing Dependency: nss = 3.13.1-7.el6_2 for package: nss-tools-3.13.1-7.el6_2.i686\n--> Processing Dependency: libnssutil3.so(NSSUTIL_3.13) for package: nss-tools-3.13.1-7.el6_2.i686\n--> Processing Dependency: libnss3.so(NSS_3.13) for package: nss-tools-3.13.1-7.el6_2.i686\n---> Package perl-CGI.i686 0:3.51-119.el6_1.1 will be installed\n---> Package perl-Mozilla-LDAP.i686 0:1.5.3-4.el6 will be installed\n---> Package policycoreutils-python.i686 0:2.0.83-19.21.el6_2 will be installed\n--> Processing Dependency: policycoreutils = 2.0.83-19.21.el6_2 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686\n--> Processing Dependency: audit-libs-python >= 1.4.2-1 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686\n--> Processing Dependency: libsemanage-python >= 2.0.43-4 for package: policycoreutils-python-2.0.83-19.21.el6_2.i686\n--> Processing Dependency: setools-libs-python for package: policycoreutils-python-2.0.83-19.21.el6_2.i686\n--> Processing Dependency: libcgroup for package: policycoreutils-python-2.0.83-19.21.el6_2.i686\n---> Package svrcore.i686 0:4.0.4-5.1.el6 will be installed\n--> Running transaction check\n---> Package audit-libs-python.i686 0:2.1.3-3.el6 will be installed\n---> Package giflib.i686 0:4.1.6-3.1.el6 will be installed\n---> Package java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6 will be installed\n--> Processing Dependency: sinjdoc for package: java-1.5.0-gcj-1.5.0.0-29.1.el6.i686\n---> Package libcgroup.i686 0:0.37-3.el6 will be installed\n---> Package libgcj.i686 0:4.4.6-3.el6 will be installed\n--> Processing Dependency: zip >= 2.1 for package: libgcj-4.4.6-3.el6.i686\n---> Package libsemanage-python.i686 0:2.0.43-4.1.el6 will be installed\n---> Package lm_sensors-libs.i686 0:3.1.1-10.el6 will be installed\n---> Package nss.i686 0:3.12.10-17.el6_2 will be updated\n--> Processing Dependency: nss = 3.12.10-17.el6_2 for package: nss-sysinit-3.12.10-17.el6_2.i686\n---> Package nss.i686 0:3.13.1-7.el6_2 will be an update\n--> Processing Dependency: nspr >= 4.8.9 for package: nss-3.13.1-7.el6_2.i686\n---> Package nss-util.i686 0:3.12.10-2.el6 will be updated\n---> Package nss-util.i686 0:3.13.1-3.el6_2 will be an update\n---> Package policycoreutils.i686 0:2.0.83-19.18.el6 will be updated\n---> Package policycoreutils.i686 0:2.0.83-19.21.el6_2 will be an update\n---> Package rhino.noarch 0:1.7-0.7.r2.2.el6 will be installed\n--> Processing Dependency: jline for package: rhino-1.7-0.7.r2.2.el6.noarch\n---> Package setools-libs-python.i686 0:3.3.7-4.el6 will be installed\n--> Processing Dependency: setools-libs = 3.3.7-4.el6 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libapol.so.4 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libsefs.so.4 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libpoldiff.so.1 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libseaudit.so.4(VERS_4.2) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libseaudit.so.4 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libapol.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libqpol.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libqpol.so.1 for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libsefs.so.4(VERS_4.0) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libpoldiff.so.1(VERS_1.3) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libapol.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libqpol.so.1(VERS_1.4) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libseaudit.so.4(VERS_4.1) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libpoldiff.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686\n--> Processing Dependency: libqpol.so.1(VERS_1.2) for package: setools-libs-python-3.3.7-4.el6.i686\n---> Package tzdata-java.noarch 0:2011n-2.el6 will be installed\n--> Running transaction check\n---> Package jline.noarch 0:0.9.94-0.8.el6 will be installed\n---> Package nspr.i686 0:4.8.8-3.el6 will be updated\n---> Package nspr.i686 0:4.8.9-3.el6_2 will be an update\n---> Package nss-sysinit.i686 0:3.12.10-17.el6_2 will be updated\n---> Package nss-sysinit.i686 0:3.13.1-7.el6_2 will be an update\n---> Package setools-libs.i686 0:3.3.7-4.el6 will be installed\n---> Package sinjdoc.i686 0:0.5-9.1.el6 will be installed\n--> Processing Dependency: java_cup >= 0.10 for package: sinjdoc-0.5-9.1.el6.i686\n---> Package zip.i686 0:3.0-1.el6 will be installed\n--> Running transaction check\n---> Package java_cup.i686 1:0.10k-5.el6 will be installed\n--> Finished Dependency Resolution\n\nDependencies Resolved\n\n====================================================================================================\n Package Arch Version Repository Size\n====================================================================================================\nInstalling:\n 389-ds noarch 1.2.2-1.el6 epel 9.9 k\n openldap-clients i686 2.4.23-20.el6 CentOS6.2-Repository 155 k\nInstalling for dependencies:\n 389-admin i686 1.1.25-1.el6 epel 341 k\n 389-admin-console noarch 1.1.8-1.el6 epel 202 k\n 389-admin-console-doc noarch 1.1.8-1.el6 epel 43 k\n 389-adminutil i686 1.1.14-2.el6 epel 64 k\n 389-console noarch 1.1.7-1.el6 epel 72 k\n 389-ds-base i686 1.2.9.14-1.el6_2.2 updates 1.4 M\n 389-ds-base-libs i686 1.2.9.14-1.el6_2.2 updates 369 k\n 389-ds-console noarch 1.2.6-1.el6 epel 1.4 M\n 389-ds-console-doc noarch 1.2.6-1.el6 epel 55 k\n 389-dsgw i686 1.1.7-2.el6 epel 460 k\n audit-libs-python i686 2.1.3-3.el6 CentOS6.2-Repository 56 k\n cyrus-sasl-gssapi i686 2.1.23-13.el6 CentOS6.2-Repository 33 k\n cyrus-sasl-md5 i686 2.1.23-13.el6 CentOS6.2-Repository 46 k\n giflib i686 4.1.6-3.1.el6 CentOS6.2-Repository 37 k\n idm-console-framework noarch 1.1.7-2.el6 epel 1.1 M\n java-1.5.0-gcj i686 1.5.0.0-29.1.el6 CentOS6.2-Repository 138 k\n java-1.6.0-openjdk i686 1:1.6.0.0-1.43.1.10.6.el6_2 updates 26 M\n java_cup i686 1:0.10k-5.el6 CentOS6.2-Repository 178 k\n jline noarch 0.9.94-0.8.el6 CentOS6.2-Repository 86 k\n jpackage-utils noarch 1.7.5-3.12.el6 CentOS6.2-Repository 59 k\n jss i686 4.2.6-20.el6 CentOS6.2-Repository 745 k\n ldapjdk i686 4.18-6.el6 CentOS6.2-Repository 749 k\n libcgroup i686 0.37-3.el6 CentOS6.2-Repository 102 k\n libgcj i686 4.4.6-3.el6 CentOS6.2-Repository 17 M\n libicu i686 4.2.1-9.1.el6_2 updates 5.0 M\n libsemanage-python i686 2.0.43-4.1.el6 CentOS6.2-Repository 80 k\n lm_sensors-libs i686 3.1.1-10.el6 CentOS6.2-Repository 36 k\n mod_nss i686 1.0.8-13.el6 CentOS6.2-Repository 82 k\n net-snmp-libs i686 1:5.5-37.el6_2.1 updates 1.5 M\n nss-tools i686 3.13.1-7.el6_2 updates 741 k\n perl-CGI i686 3.51-119.el6_1.1 CentOS6.2-Repository 206 k\n perl-Mozilla-LDAP i686 1.5.3-4.el6 CentOS6.2-Repository 161 k\n policycoreutils-python i686 2.0.83-19.21.el6_2 updates 338 k\n rhino noarch 1.7-0.7.r2.2.el6 CentOS6.2-Repository 778 k\n setools-libs i686 3.3.7-4.el6 CentOS6.2-Repository 400 k\n setools-libs-python i686 3.3.7-4.el6 CentOS6.2-Repository 210 k\n sinjdoc i686 0.5-9.1.el6 CentOS6.2-Repository 646 k\n svrcore i686 4.0.4-5.1.el6 CentOS6.2-Repository 15 k\n tzdata-java noarch 2011n-2.el6 updates 153 k\n zip i686 3.0-1.el6 CentOS6.2-Repository 252 k\nUpdating for dependencies:\n nspr i686 4.8.9-3.el6_2 updates 113 k\n nss i686 3.13.1-7.el6_2 updates 763 k\n nss-sysinit i686 3.13.1-7.el6_2 updates 30 k\n nss-util i686 3.13.1-3.el6_2 updates 52 k\n policycoreutils i686 2.0.83-19.21.el6_2 updates 640 k\n\nTransaction Summary\n====================================================================================================\nInstall 42 Package(s)\nUpgrade 5 Package(s)\n\nTotal download size: 63 M\nDownloading Packages:\n(1\/47): 389-admin-1.1.25-1.el6.i686.rpm | 341 kB 00:03\n(2\/47): 389-admin-console-1.1.8-1.el6.noarch.rpm | 202 kB 00:01\n(3\/47): 389-admin-console-doc-1.1.8-1.el6.noarch.rpm | 43 kB 00:00\n(4\/47): 389-adminutil-1.1.14-2.el6.i686.rpm | 64 kB 00:00\n(5\/47): 389-console-1.1.7-1.el6.noarch.rpm | 72 kB 00:00\n(6\/47): 389-ds-1.2.2-1.el6.noarch.rpm | 9.9 kB 00:00\n(7\/47): 389-ds-base-1.2.9.14-1.el6_2.2.i686.rpm | 1.4 MB 00:11\n(8\/47): 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686.rpm | 369 kB 00:03\n(9\/47): 389-ds-console-1.2.6-1.el6.noarch.rpm | 1.4 MB 00:13\n(10\/47): 389-ds-console-doc-1.2.6-1.el6.noarch.rpm | 55 kB 00:00\n(11\/47): 389-dsgw-1.1.7-2.el6.i686.rpm | 460 kB 00:03\n(12\/47): idm-console-framework-1.1.7-2.el6.noarch.rpm | 1.1 MB 00:08\n(13\/47): java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686.rpm | 26 MB 03:56\n(14\/47): libicu-4.2.1-9.1.el6_2.i686.rpm | 5.0 MB 00:44\n(15\/47): net-snmp-libs-5.5-37.el6_2.1.i686.rpm | 1.5 MB 00:13\n(16\/47): nspr-4.8.9-3.el6_2.i686.rpm | 113 kB 00:00\n(17\/47): nss-3.13.1-7.el6_2.i686.rpm | 763 kB 00:06\n(18\/47): nss-sysinit-3.13.1-7.el6_2.i686.rpm | 30 kB 00:00\n(19\/47): nss-tools-3.13.1-7.el6_2.i686.rpm | 741 kB 00:06\n(20\/47): nss-util-3.13.1-3.el6_2.i686.rpm | 52 kB 00:00\n(21\/47): policycoreutils-2.0.83-19.21.el6_2.i686.rpm | 640 kB 00:05\n(22\/47): policycoreutils-python-2.0.83-19.21.el6_2.i686.rpm | 338 kB 00:03\n(23\/47): tzdata-java-2011n-2.el6.noarch.rpm | 153 kB 00:01\n----------------------------------------------------------------------------------------------------\nTotal 174 kB\/s | 63 MB 06:11\nRunning rpm_check_debug\nRunning Transaction Test\nTransaction Test Succeeded\nRunning Transaction\n Installing : jpackage-utils-1.7.5-3.12.el6.noarch 1\/52\n Installing : perl-CGI-3.51-119.el6_1.1.i686 2\/52\n Installing : jline-0.9.94-0.8.el6.noarch 3\/52\n Installing : rhino-1.7-0.7.r2.2.el6.noarch 4\/52\n Installing : tzdata-java-2011n-2.el6.noarch 5\/52\n Updating : nspr-4.8.9-3.el6_2.i686 6\/52\n Updating : nss-util-3.13.1-3.el6_2.i686 7\/52\n Updating : nss-sysinit-3.13.1-7.el6_2.i686 8\/52\n Updating : nss-3.13.1-7.el6_2.i686 9\/52\n Installing : libicu-4.2.1-9.1.el6_2.i686 10\/52\n Installing : perl-Mozilla-LDAP-1.5.3-4.el6.i686 11\/52\n Installing : nss-tools-3.13.1-7.el6_2.i686 12\/52\n Installing : 389-adminutil-1.1.14-2.el6.i686 13\/52\n Installing : svrcore-4.0.4-5.1.el6.i686 14\/52\n Updating : policycoreutils-2.0.83-19.21.el6_2.i686 15\/52\n Installing : 389-ds-base-libs-1.2.9.14-1.el6_2.2.i686 16\/52\n Installing : mod_nss-1.0.8-13.el6.i686 17\/52\n Installing : openldap-clients-2.4.23-20.el6.i686 18\/52\n Installing : lm_sensors-libs-3.1.1-10.el6.i686 19\/52\n Installing : 1:net-snmp-libs-5.5-37.el6_2.1.i686 20\/52\n Installing : giflib-4.1.6-3.1.el6.i686 21\/52\n Installing : zip-3.0-1.el6.i686 22\/52\n Installing : libgcj-4.4.6-3.el6.i686 23\/52\n Installing : 1:java-1.6.0-openjdk-1.6.0.0-1.43.1.10.6.el6_2.i686 24\/52\n Installing : java-1.5.0-gcj-1.5.0.0-29.1.el6.i686 25\/52\n Installing : 1:java_cup-0.10k-5.el6.i686 26\/52\n Installing : sinjdoc-0.5-9.1.el6.i686 27\/52\n Installing : jss-4.2.6-20.el6.i686 28\/52\n Installing : ldapjdk-4.18-6.el6.i686 29\/52\n Installing : idm-console-framework-1.1.7-2.el6.noarch 30\/52\n Installing : 389-console-1.1.7-1.el6.noarch 31\/52\n Installing : cyrus-sasl-gssapi-2.1.23-13.el6.i686 32\/52\n Installing : setools-libs-3.3.7-4.el6.i686 33\/52\n Installing : setools-libs-python-3.3.7-4.el6.i686 34\/52\n Installing : cyrus-sasl-md5-2.1.23-13.el6.i686 35\/52\n Installing : libcgroup-0.37-3.el6.i686 36\/52\n Installing : audit-libs-python-2.1.3-3.el6.i686 37\/52\n Installing : libsemanage-python-2.0.43-4.1.el6.i686 38\/52\n Installing : policycoreutils-python-2.0.83-19.21.el6_2.i686 39\/52\n Installing : 389-ds-base-1.2.9.14-1.el6_2.2.i686 40\/52\n Installing : 389-admin-1.1.25-1.el6.i686 41\/52\n Installing : 389-admin-console-1.1.8-1.el6.noarch 42\/52\n Installing : 389-ds-console-1.2.6-1.el6.noarch 43\/52\n Installing : 389-ds-console-doc-1.2.6-1.el6.noarch 44\/52\n Installing : 389-admin-console-doc-1.1.8-1.el6.noarch 45\/52\n Installing : 389-dsgw-1.1.7-2.el6.i686 46\/52\n Installing : 389-ds-1.2.2-1.el6.noarch 47\/52\n Cleanup : nss-sysinit-3.12.10-17.el6_2.i686 48\/52\n Cleanup : nss-3.12.10-17.el6_2.i686 49\/52\n Cleanup : nss-util-3.12.10-2.el6.i686 50\/52\n Cleanup : nspr-4.8.8-3.el6.i686 51\/52\n Cleanup : policycoreutils-2.0.83-19.18.el6.i686 52\/52\n\nInstalled:\n 389-ds.noarch 0:1.2.2-1.el6 openldap-clients.i686 0:2.4.23-20.el6\n\nDependency Installed:\n 389-admin.i686 0:1.1.25-1.el6 389-admin-console.noarch 0:1.1.8-1.el6\n 389-admin-console-doc.noarch 0:1.1.8-1.el6 389-adminutil.i686 0:1.1.14-2.el6\n 389-console.noarch 0:1.1.7-1.el6 389-ds-base.i686 0:1.2.9.14-1.el6_2.2\n 389-ds-base-libs.i686 0:1.2.9.14-1.el6_2.2 389-ds-console.noarch 0:1.2.6-1.el6\n 389-ds-console-doc.noarch 0:1.2.6-1.el6 389-dsgw.i686 0:1.1.7-2.el6\n audit-libs-python.i686 0:2.1.3-3.el6 cyrus-sasl-gssapi.i686 0:2.1.23-13.el6\n cyrus-sasl-md5.i686 0:2.1.23-13.el6 giflib.i686 0:4.1.6-3.1.el6\n idm-console-framework.noarch 0:1.1.7-2.el6 java-1.5.0-gcj.i686 0:1.5.0.0-29.1.el6\n java-1.6.0-openjdk.i686 1:1.6.0.0-1.43.1.10.6.el6_2 java_cup.i686 1:0.10k-5.el6\n jline.noarch 0:0.9.94-0.8.el6 jpackage-utils.noarch 0:1.7.5-3.12.el6\n jss.i686 0:4.2.6-20.el6 ldapjdk.i686 0:4.18-6.el6\n libcgroup.i686 0:0.37-3.el6 libgcj.i686 0:4.4.6-3.el6\n libicu.i686 0:4.2.1-9.1.el6_2 libsemanage-python.i686 0:2.0.43-4.1.el6\n lm_sensors-libs.i686 0:3.1.1-10.el6 mod_nss.i686 0:1.0.8-13.el6\n net-snmp-libs.i686 1:5.5-37.el6_2.1 nss-tools.i686 0:3.13.1-7.el6_2\n perl-CGI.i686 0:3.51-119.el6_1.1 perl-Mozilla-LDAP.i686 0:1.5.3-4.el6\n policycoreutils-python.i686 0:2.0.83-19.21.el6_2 rhino.noarch 0:1.7-0.7.r2.2.el6\n setools-libs.i686 0:3.3.7-4.el6 setools-libs-python.i686 0:3.3.7-4.el6\n sinjdoc.i686 0:0.5-9.1.el6 svrcore.i686 0:4.0.4-5.1.el6\n tzdata-java.noarch 0:2011n-2.el6 zip.i686 0:3.0-1.el6\n\nDependency Updated:\n nspr.i686 0:4.8.9-3.el6_2 nss.i686 0:3.13.1-7.el6_2\n nss-sysinit.i686 0:3.13.1-7.el6_2 nss-util.i686 0:3.13.1-3.el6_2\n policycoreutils.i686 0:2.0.83-19.21.el6_2\n\nComplete!<\/pre>\n3.0 Setup and Configure 389 Directory Server on CentOS 6.2<\/h2>\n
On previous post, i already shows you on how to tuning and install 389 Directory Server on linux CentOS 6.2 server using EPEL repository. Again, before proceed to setup and configure 389 Directory Server on linux CentOS 6.2 server, please make sure that the hostname and FQDN also has been configured correctly.<\/p>\n
3.1 Run the configuration script:<\/h3>\n
[root@centos62 ~]# setup-ds-admin.pl<\/pre>\nExamples complete setup and 389 directory configuration :<\/p>\n
[root@centos62 ~]# setup-ds-admin.pl\n\n==============================================================================\nThis program will set up the 389 Directory and Administration Servers.\n\nIt is recommended that you have \"root\" privilege to set up the software.\nTips for using this program:\n - Press \"Enter\" to choose the default and go to the next screen\n - Type \"Control-B\" then \"Enter\" to go back to the previous screen\n - Type \"Control-C\" to cancel the setup program\n\nWould you like to continue with set up? [yes]: yes\n\n==============================================================================\nYour system has been scanned for potential problems, missing patches,\netc. The following output is a report of the items found that need to\nbe addressed before running this software in a production\nenvironment.\n\n389 Directory Server system tuning analysis version 10-AUGUST-2007.\n\nNOTICE : System is i686-unknown-linux2.6.32-220.4.1.el6.i686 (1 processor).\n\nWould you like to continue? [no]: yes\n\n==============================================================================\nChoose a setup type:\n\n 1. Express\n Allows you to quickly set up the servers using the most\n common options and pre-defined defaults. Useful for quick\n evaluation of the products.\n\n 2. Typical\n Allows you to specify common defaults and options.\n\n 3. Custom\n Allows you to specify more advanced options. This is\n recommended for experienced server administrators only.\n\nTo accept the default shown in brackets, press the Enter key.\n\nChoose a setup type [2]:\n\n==============================================================================\nEnter the fully qualified domain name of the computer\non which you're setting up server software. Using the form\n.\nExample: eros.example.com.\n\nTo accept the default shown in brackets, press the Enter key.\n\nWarning: This step may take a few minutes if your DNS servers\ncan not be reached or if DNS is not configured correctly. If\nyou would rather not wait, hit Ctrl-C and run this program again\nwith the following command line option to specify the hostname:\n\n General.FullMachineName=your.hostname.domain.name\n\nComputer name [centos62.ehowstuff.local]:\n\n==============================================================================\nThe servers must run as a specific user in a specific group.\nIt is strongly recommended that this user should have no privileges\non the computer (i.e. a non-root user). The setup procedure\nwill give this user\/group some permissions in specific paths\/files\nto perform server-specific operations.\n\nIf you have not yet created a user and group for the servers,\ncreate this user and group using your native operating\nsystem utilities.\n\nSystem User [nobody]:\nSystem Group [nobody]:\n\n==============================================================================\nServer information is stored in the configuration directory server.\nThis information is used by the console and administration server to\nconfigure and manage your servers. If you have already set up a\nconfiguration directory server, you should register any servers you\nset up or create with the configuration server. To do so, the\nfollowing information about the configuration server is required: the\nfully qualified host name of the form\n.(e.g. hostname.example.com), the port number\n(default 389), the suffix, the DN and password of a user having\npermission to write the configuration information, usually the\nconfiguration directory administrator, and if you are using security\n(TLS\/SSL). If you are using TLS\/SSL, specify the TLS\/SSL (LDAPS) port\nnumber (default 636) instead of the regular LDAP port number, and\nprovide the CA certificate (in PEM\/ASCII format).\n\nIf you do not yet have a configuration directory server, enter 'No' to\nbe prompted to set up one.\n\nDo you want to register this software with an existing\nconfiguration directory server? [no]:\n\n==============================================================================\nPlease enter the administrator ID for the configuration directory\nserver. This is the ID typically used to log in to the console. You\nwill also be prompted for the password.\n\nConfiguration directory server\nadministrator ID [admin]:\nPassword:\nPassword (confirm):\n\n==============================================================================\nThe information stored in the configuration directory server can be\nseparated into different Administration Domains. If you are managing\nmultiple software releases at the same time, or managing information\nabout multiple domains, you may use the Administration Domain to keep\nthem separate.\n\nIf you are not using administrative domains, press Enter to select the\ndefault. Otherwise, enter some descriptive, unique name for the\nadministration domain, such as the name of the organization\nresponsible for managing the domain.\n\nAdministration Domain [ehowstuff.local]:\n\n==============================================================================\nThe standard directory server network port number is 389. However, if\nyou are not logged as the superuser, or port 389 is in use, the\ndefault value will be a random unused port number greater than 1024.\nIf you want to use port 389, make sure that you are logged in as the\nsuperuser, that port 389 is not in use.\n\nDirectory server network port [389]:\n\n==============================================================================\nEach instance of a directory server requires a unique identifier.\nThis identifier is used to name the various\ninstance specific files and directories in the file system,\nas well as for other uses as a server instance identifier.\n\nDirectory server identifier [centos62]:\n\n==============================================================================\nThe suffix is the root of your directory tree. The suffix must be a valid DN.\nIt is recommended that you use the dc=domaincomponent suffix convention.\nFor example, if your domain is example.com,\nyou should use dc=example,dc=com for your suffix.\nSetup will create this initial suffix for you,\nbut you may have more than one suffix.\nUse the directory server utilities to create additional suffixes.\n\nSuffix [dc=ehowstuff, dc=local]:\n\n==============================================================================\nCertain directory server operations require an administrative user.\nThis user is referred to as the Directory Manager and typically has a\nbind Distinguished Name (DN) of cn=Directory Manager.\nYou will also be prompted for the password for this user. The password must\nbe at least 8 characters long, and contain no spaces.\nPress Control-B or type the word \"back\", then Enter to back up and start over.\n\nDirectory Manager DN [cn=Directory Manager]:\nPassword:\nPassword (confirm):\n\n==============================================================================\nThe Administration Server is separate from any of your web or application\nservers since it listens to a different port and access to it is\nrestricted.\n\nPick a port number between 1024 and 65535 to run your Administration\nServer on. You should NOT use a port number which you plan to\nrun a web or application server on, rather, select a number which you\nwill remember and which will not be used for anything else.\n\nAdministration port [9830]:\n\n==============================================================================\nThe interactive phase is complete. The script will now set up your\nservers. Enter No or go Back if you want to change something.\n\nAre you ready to set up your servers? [yes]:\nCreating directory server . . .\nYour new DS instance 'centos62' was successfully created.\nCreating the configuration directory server . . .\nBeginning Admin Server creation . . .\nCreating Admin Server files and directories . . .\nUpdating adm.conf . . .\nUpdating admpw . . .\nRegistering admin server with the configuration directory server . . .\nUpdating adm.conf with information from configuration directory server . . .\nUpdating the configuration for the httpd engine . . .\nStarting admin server . . .\noutput: Starting dirsrv-admin:\noutput: [ OK ]\nThe admin server was successfully started.\nAdmin server was successfully created, configured, and started.\nExiting . . .\nLog file is '\/tmp\/setup1EmS4N.log'<\/pre>\n4.0 Start, Stop and Restart 389 Directory Server on CentOS 6.2<\/h2>\n
This post will guide you on how to start, stop, restart and check dirsrv status for 389 Directory Server on linux CentOS 6.2 server. This post assumed that you have already installed and properly configured the 389 Directory Server on CentOS 6.2.<\/p>\n
4.1 Some of the dirsrv usage for 389 Directory Server :<\/h3>\n
Usage: \/etc\/init.d\/dirsrv {start|stop|status|restart|condrestart} [instance-name]<\/pre>\n4.2 How to start 389 Directory Server :<\/h3>\n
[root@centos62 ~]# \/etc\/init.d\/dirsrv start\nStarting dirsrv:\n centos62... [ OK ]<\/pre>\n4.3 How to stop 389 Directory Server :<\/h3>\n
[root@centos62 ~]# \/etc\/init.d\/dirsrv stop\nShutting down dirsrv:\n centos62... [ OK ]<\/pre>\n4.4 How to restart 389 Directory Server :<\/h3>\n
[root@centos62 ~]# \/etc\/init.d\/dirsrv restart\nShutting down dirsrv:\n centos62... [ OK ]<\/pre>\n4.5 How to check the status 389 Directory Server :<\/h3>\n
[root@centos62 ~]# \/etc\/init.d\/dirsrv status\ndirsrv centos62 (pid 1296) is running...<\/pre>\n5.0 Configure Iptables Firewall for 389 Directory Server on CentOS 6.2<\/h2>\n
I will show the ports that need to be by passed in iptables firewall in order to make 389 Directory server accessible and working perfectly. Before the Windows Console (installed 389 Console.msi) from client’ PC connecting to 389 administration server, there are 3 important ports has to opened from iptables firewall. This will allow linux administrator or LDAP administrator to perform LDAP server search query or linux administration’s task. There are three(3) ports that are normally should be opened on 389 Directory Server.<\/p>\n
a) Port 389 (ldap)
\nb) Port 636 (ldaps – only if using TLS\/SSL)
\nc) Admin server port (9830 by default)<\/p>\n5.1 Run netstat command to see opened port :<\/h3>\n
\n[root@centos62 ~]# netstat -plunt\nActive Internet connections (only servers)\nProto Recv-Q Send-Q Local Address Foreign Address State PID\/Program name\ntcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1105\/sshd\ntcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1140\/postmaster\ntcp 0 0 0.0.0.0:9830 0.0.0.0:* LISTEN 1415\/httpd.worker\ntcp 0 0 :::22 :::* LISTEN 1105\/sshd\ntcp 0 0 ::1:5432 :::* LISTEN 1140\/postmaster\ntcp 0 0 :::389 :::* LISTEN 1792\/ns-slapd\n<\/pre>\n5.2 Open the iptables firewall configuration file then enable port 389, 636 and 9830 go through iptables firewall :<\/h3>\n
\n[root@centos62 ~]# vi \/etc\/sysconfig\/iptables\n<\/pre>\n5.3 Add these three(3) lines:<\/h3>\n
\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 636 -j ACCEPT\n-A INPUT -m state --state NEW -m tcp -p tcp --dport 9830 -j ACCEPT\n<\/pre>\n5.4 Then restart the iptables firewall :<\/h3>\n
\n[root@centos62 ~]# service iptables restart\n<\/pre>\nHope this complete steps may help you to prepare, tuning, install and configure 389 directory on your linux server.<\/p>\n","protected":false},"excerpt":{"rendered":"
389 Directory Server 1.0 Tuning 389 Directory Server on CentOS 6.2 This post will share with you on how to perform system tuning analysis, install and configure 389 Directory Server…<\/p>\n","protected":false},"author":6,"featured_media":717,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":0,"footnotes":""},"categories":[1102],"tags":[1178,1190,1244,1253,1536,1546,1825],"class_list":["post-3122","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-389-directory-server","tag-389-directory","tag-analysis","tag-centos","tag-centos-6-2","tag-linux","tag-linux-utilities","tag-system-tuning"],"_links":{"self":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/3122","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/comments?post=3122"}],"version-history":[{"count":0,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/3122\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media\/717"}],"wp:attachment":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media?parent=3122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/categories?post=3122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/tags?post=3122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}