Someone in the linuxQuestion recommended me to just start
389-ds-admin.plwhich will take care of Directory Server and Admin
Server too. Is it
correct?
So, I ran the following commands
Code:
[root at 389-ds init.d]# service dirsrv stop
Shutting down dirsrv:
389-ds... [ OK ]
[root at 389-ds ~]# /usr/sbin/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]: yes
==============================================================================
BY SETTING UP AND USING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY
AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE
LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS
OF THIS AGREEMENT, PLEASE DO NOT SET UP OR USE THIS SOFTWARE.
Do you agree to the license terms? [no]: yes
==============================================================================
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 10-AUGUST-2007.
NOTICE : System is i686-unknown-linux2.6.18-164.el5 (1 processor).
ERROR : Only 249MB of physical memory is available on the system. 256MB is
the
recommended minimum. 1024MB is recommended for best performance on large
production system.
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 (hard limit) available, which
limit the number of simultaneous connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
ERROR : The above errors MUST be corrected before proceeding.
Would you like to continue? [no]: yes
==============================================================================
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]: 2
==============================================================================
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.
Computer name [389-ds.sap.com]:
==============================================================================
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]: fds
System Group [nobody]: fds
==============================================================================
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]: yes
==============================================================================
Please specify the information about your configuration directory
server. The following information is required:
- host (fully qualified), port (non-secure or secure), suffix,
protocol (ldap or ldaps) - this information should be provided in the
form of an LDAP url e.g. for non-secure
ldap://host.example.com:389/o=NetscapeRoot
or for secure
ldaps://host.example.com:636/o=NetscapeRoot
- admin ID and password
- admin domain
- a CA certificate file may be required if you choose to use ldaps and
security has not yet been configured - the file must be in PEM/ASCII
format - specify the absolute path and filename
Configuration directory server URL [ldap://389-ds.sap.com:389/o=NetscapeRoot
]:
Configuration directory server admin ID [admin]:
Configuration directory server admin password:
Configuration directory server admin domain [sapient.com]:
The server 'ldap://389-ds.sap.com:389/o=NetscapeRoot' is not reachable.
Error: unknown error
Please try again, in case you mis-typed something.
Configuration directory server URL [ldap://389-ds.sap.com:389/o=NetscapeRoot
]:
[root at 389-ds ~]#Am I missing anything?
On Sat, Jan 9, 2010 at 12:56 PM, Ajeet S Raina <ajeetraina at gmail.com> wrote:
>
>
> Guys,
>
> I have been confused with the overall new 389 DS Server Setup.
> All I did upto now is:
>
> yum install 389-ds
>
> and it did all the installation correctly.
> Then, I ran:
> /usr/sbin/setup-ds.pl
>
> It too went fine.
>
> All I need is Setup 389 Server with SSL.I did went through
> http://directory.fedoraproject.org/wiki/Howto:SSL but no Idea how to
> proceed.
>
> I am confused with the following points:
>
> 1. Do I also need to run *setup-ds-admin.pl* and *setup-ds-dsgw* too?
>
> I tried running setup-ds-admin.pl and it stucked at :
>
> The server 'ldap://389-ds.sap.com:45474/o=NetscapeRoot' is not reachable.
> Error: unknown error.
>
> 2. When Should I run the setupssl2.sh script? After running the above
> setup-* scripts?
> What changes I need to make on the script?
>
--
?It is not possible to rescue everyone who is caught in the Windows
quicksand
--Make sure you are on solid Linux ground before trying.?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20100109/3a042122/attachment.html
