From Fedora Project Wiki

No edit summary
(Update installation instructions)
 
(2 intermediate revisions by the same user not shown)
Line 2: Line 2:
|description=
|description=


This test case tests the installation of 389 Directory Server Instance.  
This test case tests the installation of 389 Directory Server instance.  


NOTE :: This includes only Instance setup testing, not the console.
NOTE: This includes only instance setup testing, not the console.
Full documentation on setting up a 389 Directory Server instance can be found [http://directory.fedoraproject.org/wiki/Install_Guide here] if needed.
Full documentation on setting up 389 Directory Server instance can be found [https://www.port389.org/docs/389ds/howto/quickstart.html here] if needed.


|actions=
|actions=
1. Install 389 ds package.<br>  
1. Install 389-ds-base package.<br>  
<pre>yum install 389-ds-base</pre>  
<pre>dnf install 389-ds-base</pre>  
This will install 389-ds-base and 389-ds-base-libs as dependency package.
This will install 389-ds-base, 389-ds-base-libs and their dependencies.
Package related information [http://directory.fedoraproject.org/wiki/Download RPM Download Help]


2. Now setup the Directory Server instance using setup-ds.pl
2. Now setup the Directory Server instance using `dscreate`


<pre>setup-ds.pl</pre>
<pre>dscreate interactive</pre>


This will ask you for some configuration questions, carefully read and answer. Optionally you can make answer file to setup the instance.
This will ask you for some configuration questions, carefully read and answer. Optionally you can make answer file to setup the instance.
Line 21: Line 20:
3. At the end of the setup, a message will display as:  
3. At the end of the setup, a message will display as:  


<pre>Your new DS instance 'dhcp201-149_1' was successfully created.
<pre>
Exiting . . .
Starting installation ...
Log file is '/tmp/setupYzgw2O.log</pre>
Validate installation settings ...
Create file system structures ...
Create self-signed certificate database ...
Perform SELinux labeling ...
Create database backend: dc=example,dc=com ...
Perform post-installation tasks ...
Completed installation for instance: slapd-localhost
</pre>


This means your DS instance is ready.
This means your DS instance is ready.
Line 31: Line 37:
#One can check the process by checking slapd process should be running, as::
#One can check the process by checking slapd process should be running, as::


<pre>[root@dhcp201-149 ~]# ps -aef | grep slapd<br>nobody&nbsp;&nbsp;&nbsp; 4868&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp; 0 17:57 ?&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 00:00:00 /usr/sbin/ns-slapd -D /etc/dirsrv/slapd-dhcp201-149_1 -i /var/run/dirsrv/slapd-dhcp201-149_1.pid -w /var/run/dirsrv/slapd-dhcp201-149_1.startpid<br></pre>
<pre>dsctl localhost status
Instance "localhost" is running
</pre>


}}
}}


[[Category:Package_389-ds-base_test_cases]]
[[Category:Package_389-ds-base_test_cases]]

Latest revision as of 12:22, 30 July 2024

Description

This test case tests the installation of 389 Directory Server instance.

NOTE: This includes only instance setup testing, not the console. Full documentation on setting up 389 Directory Server instance can be found here if needed.


How to test

1. Install 389-ds-base package.

dnf install 389-ds-base

This will install 389-ds-base, 389-ds-base-libs and their dependencies.

2. Now setup the Directory Server instance using dscreate

dscreate interactive

This will ask you for some configuration questions, carefully read and answer. Optionally you can make answer file to setup the instance.

3. At the end of the setup, a message will display as:

Starting installation ...
Validate installation settings ...
Create file system structures ...
Create self-signed certificate database ...
Perform SELinux labeling ...
Create database backend: dc=example,dc=com ...
Perform post-installation tasks ...
Completed installation for instance: slapd-localhost

This means your DS instance is ready.

Expected Results

  1. Directory Server should be up and running
  2. One can check the process by checking slapd process should be running, as::
dsctl localhost status
Instance "localhost" is running