Marc Sauton <msauton@xxxxxxxxxx> escribió:
On 07/21/2011 03:04 PM, Michel Bulgado wrote:
Hello
Recently I just installed 389-ds-1.2.1-1.el5.noarch from EPEL repo,
because in my company we use Active Directory and want to migrate to Linux
I have installed CentOS 5.6 x86_64.
The problem persists when trying to run setup-ds-admin.pl and at the
very end I get an error message.
[11/07/21, 17:08:27] - [Setup] Info Are you ready to set-up your servers?
[11/07/21, 17:08:28] - [Setup] Info yes
[11/07/21, 17:08:28] - [Setup] Info Creating directory server. . .
[11/07/21, 17:08:29] - [Setup] Info Could not import LDIF file '/ tmp /
ldifESlBSW.ldif'. Error: 65280. Output: Importing data ...
[11/07/21, 17:08:29] - [Setup] Fatal Error: Could not create directory
server instance 'michel'.
[11/07/21, 17:08:29] - [Setup] Fatal Exiting. . .
Log file is '/ tmp/setup5jSSdH.log'
Maybe you can help me, google searching for someone I saw the same
problem happened to him and recommended him to move or delete the file
10-presence.ldif directory schema, but that file does not exist in that
directory.
That I could be doing wrong?
Thanks
Michel
--
Review the file permissions for /tmp/ldifESlBSW.ldif, so that
ns-slapd can read it.
And maybe review the output of /tmp/setup5jSSdH.log
M.
Hi
The script ran it as root, I do not understand how you may be unable
to import the file ldiff stored in /tmp as root who runs the script
and also access any system resource.
It may be that you specify the user under which runs the 389-ds is "nobody"?
I send you the log file generated by the script.
Sorry for my english is very poor
Michel
----------------------------------------------
Webmail, servicio de correo electronico
Casa de las Americas - La Habana, Cuba.
[11/07/21:17:07:43] - [Setup] Info 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
[11/07/21:17:07:43] - [Setup] Info Would you like to continue with set up?
[11/07/21:17:07:45] - [Setup] Info yes
[11/07/21:17:07:45] - [Setup] Info 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.
[11/07/21:17:07:45] - [Setup] Info Do you agree to the license terms?
[11/07/21:17:07:47] - [Setup] Info yes
[11/07/21:17:07:47] - [Setup] Info 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 x86_64-unknown-linux2.6.18-238.12.1.el5 (2 processors).
WARNING: 992MB of physical memory is available on the system. 1024MB is recommended for best performance on large production system.
WARNING : The warning messages above should be reviewed before proceeding.
[11/07/21:17:07:47] - [Setup] Info Would you like to continue?
[11/07/21:17:07:49] - [Setup] Info yes
[11/07/21:17:07:49] - [Setup] Info 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.
[11/07/21:17:07:49] - [Setup] Info Choose a setup type
[11/07/21:17:07:51] - [Setup] Info 3
[11/07/21:17:07:51] - [Setup] Info 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
[11/07/21:17:07:51] - [Setup] Info Computer name
[11/07/21:17:07:54] - [Setup] Info michel.casa.cult.cu
[11/07/21:17:07:54] - [Setup] Info 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.
[11/07/21:17:07:54] - [Setup] Info System User
[11/07/21:17:07:55] - [Setup] Info nobody
[11/07/21:17:07:55] - [Setup] Info System Group
[11/07/21:17:07:56] - [Setup] Info nobody
[11/07/21:17:07:56] - [Setup] Info 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.
[11/07/21:17:07:56] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[11/07/21:17:07:58] - [Setup] Info no
[11/07/21:17:07:58] - [Setup] Info 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.
[11/07/21:17:07:58] - [Setup] Info Configuration directory server
administrator ID
[11/07/21:17:07:59] - [Setup] Info admin
[11/07/21:17:07:59] - [Setup] Info Password
[11/07/21:17:08:03] - [Setup] Info Password (confirm)
[11/07/21:17:08:06] - [Setup] Info 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.
[11/07/21:17:08:06] - [Setup] Info Administration Domain
[11/07/21:17:08:07] - [Setup] Info casa.cult.cu
[11/07/21:17:08:07] - [Setup] Info 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.
[11/07/21:17:08:07] - [Setup] Info Directory server network port
[11/07/21:17:08:08] - [Setup] Info 389
[11/07/21:17:08:08] - [Setup] Info 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.
[11/07/21:17:08:08] - [Setup] Info Directory server identifier
[11/07/21:17:08:09] - [Setup] Info michel
[11/07/21:17:08:09] - [Setup] Info 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.
[11/07/21:17:08:09] - [Setup] Info Suffix
[11/07/21:17:08:10] - [Setup] Info dc=casa, dc=cult, dc=cu
[11/07/21:17:08:10] - [Setup] Info 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.
[11/07/21:17:08:10] - [Setup] Info Directory Manager DN
[11/07/21:17:08:10] - [Setup] Info cn=Directory Manager
[11/07/21:17:08:10] - [Setup] Info Password
[11/07/21:17:08:14] - [Setup] Info Password (confirm)
[11/07/21:17:08:17] - [Setup] Info You may install some sample entries in this directory instance. These
entries will be installed in a separate suffix and will not interfere
with the normal operation of the directory server.
[11/07/21:17:08:17] - [Setup] Info Do you want to install the sample entries?
[11/07/21:17:08:21] - [Setup] Info no
[11/07/21:17:08:21] - [Setup] Info You may wish to populate your new directory instance with some data.
"You may already have a file in LDIF format to use or some suggested
entries can be added. If you want to import entries from an LDIF
file, you may type in the full path and filename at the prompt. If
you want the setup program to add the suggested entries, type the
word suggest at the prompt. The suggested entries are common
container entries under your specified suffix, such as ou=People and
ou=Groups, which are commonly used to hold the entries for the persons
and groups in your organization. If you do not want to add any of
these entries, type the word none at the prompt.
[11/07/21:17:08:21] - [Setup] Info Type the full path and filename, the word suggest, or the word none
[11/07/21:17:08:23] - [Setup] Info suggest
[11/07/21:17:08:23] - [Setup] Info 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.
[11/07/21:17:08:23] - [Setup] Info Administration port
[11/07/21:17:08:24] - [Setup] Info 9830
[11/07/21:17:08:24] - [Setup] Info If you want to configure the Administration Server to bind
to a specific IP address, enter the address below.
[11/07/21:17:08:24] - [Setup] Info IP address
[11/07/21:17:08:25] - [Setup] Info 0.0.0.0
[11/07/21:17:08:25] - [Setup] Info The Administration Server program runs as a certain user on your
system. This user must have permission to modify files and directories
for your Directory server as well as the Administration server. You
are strongly encouraged to use a non-privileged (i.e. non-root) user.
[11/07/21:17:08:25] - [Setup] Info Run Administration Server as
[11/07/21:17:08:27] - [Setup] Info nobody
[11/07/21:17:08:27] - [Setup] Info The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
[11/07/21:17:08:27] - [Setup] Info Are you ready to set up your servers?
[11/07/21:17:08:28] - [Setup] Info yes
[11/07/21:17:08:28] - [Setup] Info Creating directory server . . .
[11/07/21:17:08:29] - [Setup] Info Could not import LDIF file '/tmp/ldifESlBSW.ldif'. Error: 65280. Output: importing data ...
[11/07/21:17:08:29] - [Setup] Fatal Error: Could not create directory server instance 'michel'.
[11/07/21:17:08:29] - [Setup] Fatal Exiting . . .
Log file is '/tmp/setup5jSSdH.log'
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
