Автор Тема: Проблем с fedora directory server  (Прочетена 1233 пъти)


  • Участници
  • ***
  • Публикации: 5
    • Профил
Проблем с fedora directory server
« -: Jan 08, 2008, 11:39 »
От няколко дни се опитвам да си инсталирам и настроя Fedora Directory Server 1.1., но всичките ми опити до сега са безуспешни.

Тъй като нямам никакъв опит с конфигурирането на подобен род сървъри, си харесах една статия статия (http://www.linuxjournal.com/article/9517), в която подробно е обяснен процесът на нисталацията. В нея пише:
Now, with the useradd command, create an account named fedorauser under which FDS will run. After creating the account, run /opt/fedora-ds/setup/setup to launch the FDS installation script. [...] select the default Install Mode 2 - Typical. Accept all defaults during installation except for the Server and Group IDs, for which we are using the fedorauser account.

Изпълних стъпките, с разликата, че новосъздаденият потребител е fdsuser. Въпреки това не успях да стартирам сървъра: service dirsrv start всеки път връщаше грешка. С помощта на един познат успях да се справя с този проблем - оказа се, че owner на директорията /var/run/dirsr трябва да e потребител fdsuser.

Сега dirsrv демонът се стартира. Обаче изникна друг проблем : не мога да се логна в Managment Console. Ето каква грешка ми дава след като изпълня командата fedora-idm-console и въведа исканите данни:

Имате ли някаква идея каква може да е причината, за да не мога да се логна? Дали проблемът отново е свързан с правата на fdsuser?

Това са са настойките, които получих, след като следвах инструкциите на скрипта setup-ds-admin.pl

Примерен код

[08/01/07:23:14:17] - [Setup] Info This program will set up the Fedora 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

[08/01/07:23:14:17] - [Setup] Info Would you like to continue with set up?
[08/01/07:23:14:20] - [Setup] Info yes

[08/01/07:23:14:20] - [Setup] Info Do you agree to the license terms?
[08/01/07:23:14:22] - [Setup] Info yes
[08/01/07:23:14:22] - [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

Fedora Directory Server system tuning analysis version 10-AUGUST-2007.

NOTICE : System is i686-unknown-linux2.6.23.9-85.fc8 (1 processor).

WARNING: 503MB of physical memory is available on the system. 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.  

[08/01/07:23:14:22] - [Setup] Info Would you like to continue?
[08/01/07:23:14:23] - [Setup] Info yes
[08/01/07:23:14:23] - [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.

[08/01/07:23:14:23] - [Setup] Info Choose a setup type
[08/01/07:23:14:25] - [Setup] Info 2
[08/01/07:23:14:25] - [Setup] Info Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
Example: eros.example.com.

To accept the default shown in brackets, press the Enter key.

[08/01/07:23:14:25] - [Setup] Info Computer name
[08/01/07:23:14:26] - [Setup] Info localhost.localdomain
[08/01/07:23:14:26] - [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.

[08/01/07:23:14:29] - [Setup] Info System User
[08/01/07:23:14:34] - [Setup] Info fdsuser
[08/01/07:23:14:34] - [Setup] Info System Group
[08/01/07:23:14:37] - [Setup] Info fdsuser
[08/01/07:23:14:37] - [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.

[08/01/07:23:14:37] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[08/01/07:23:14:39] - [Setup] Info no
[08/01/07:23:14:39] - [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.

[08/01/07:23:14:39] - [Setup] Info Configuration directory server
administrator ID
[08/01/07:23:14:40] - [Setup] Info admin
[08/01/07:23:14:40] - [Setup] Info Password
[08/01/07:23:14:44] - [Setup] Info Password (confirm)
[08/01/07:23:14:45] - [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.

[08/01/07:23:14:45] - [Setup] Info Administration Domain
[08/01/07:23:14:46] - [Setup] Info localdomain
[08/01/07:23:14:46] - [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.

[08/01/07:23:14:46] - [Setup] Info Directory server network port
[08/01/07:23:14:47] - [Setup] Info 389
[08/01/07:23:14:47] - [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.

[08/01/07:23:14:47] - [Setup] Info Directory server identifier
[08/01/07:23:14:48] - [Setup] Info localhost
[08/01/07:23:14:48] - [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.

[08/01/07:23:14:48] - [Setup] Info Suffix
[08/01/07:23:14:52] - [Setup] Info dc=localdomain
[08/01/07:23:14:52] - [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.

[08/01/07:23:14:52] - [Setup] Info Directory Manager DN
[08/01/07:23:14:53] - [Setup] Info cn=Directory Manager
[08/01/07:23:14:53] - [Setup] Info Password
[08/01/07:23:15:02] - [Setup] Info Password (confirm)
[08/01/07:23:15:05] - [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

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.

[08/01/07:23:15:05] - [Setup] Info Administration port
[08/01/07:23:15:06] - [Setup] Info 9830
[08/01/07:23:15:06] - [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.

[08/01/07:23:15:06] - [Setup] Info Are you ready to set up your servers?
[08/01/07:23:15:10] - [Setup] Info yes
[08/01/07:23:15:10] - [Setup] Info Creating directory server . . .
[08/01/07:23:15:13] - [Setup] Info Your new DS instance 'localhost' was successfully created.
[08/01/07:23:15:13] - [Setup] Info Creating the configuration directory server . . .
[08/01/07:23:15:15] - [Setup] Info Beginning Admin Server creation . . .
[08/01/07:23:15:15] - [Setup] Info Creating Admin Server files and directories . . .
[08/01/07:23:15:15] - [Setup] Info Updating adm.conf . . .
[08/01/07:23:15:15] - [Setup] Info Updating admpw . . .
[08/01/07:23:15:15] - [Setup] Info Registering admin server with the configuration directory server . . .
[08/01/07:23:15:15] - [Setup] Info Updating adm.conf with information from configuration directory server . . .
[08/01/07:23:15:15] - [Setup] Info Updating the configuration for the httpd engine . . .
[08/01/07:23:15:15] - [Setup] Info Starting admin server . . .
[08/01/07:23:15:16] - [Setup] Info The admin server was successfully started.
[08/01/07:23:15:16] - [Setup] Info Admin server was successfully created, configured, and started.
[08/01/07:23:15:16] - [Setup] Success Exiting . . .
Log file is '/tmp/setupIqi3Gn.log'

Примерен код

AdminDomain = localdomain
SuiteSpotGroup = fdsuser
ConfigDirectoryLdapURL = ldap://localhost.localdomain:389/o=NetscapeRoot
ConfigDirectoryAdminID = admin
SuiteSpotUserID = fdsuser
ConfigDirectoryAdminPwd = <pass>
FullMachineName = localhost.localdomain

ServerAdminID = admin
ServerAdminPwd = <pass>
SysUser = fdsuser
Port = 9830

InstallLdifFile = suggest
ServerIdentifier = localhost
ServerPort = 389
AddOrgEntries = Yes
RootDN = cn=Directory Manager
RootDNPwd = <pass>
SlapdConfigForMC = yes
Suffix = dc=localdomain
UseExistingMC = 0
AddSampleEntries = No

Благодаря предварително за съветите!


Свободата не се подарява - тя се извоюва с много труд и пот.



  • Напреднали
  • *****
  • Публикации: 344
    • Профил
Проблем с fedora directory server
« Отговор #1 -: Jan 08, 2008, 15:25 »
Доколкото си спомням (отдавна беше) искаше Каноничното име при влизане ...или
нещо такова


  • Участници
  • ***
  • Публикации: 5
    • Профил
Проблем с fedora directory server
« Отговор #2 -: Jan 08, 2008, 18:12 »
Доколкото си спомням (отдавна беше) искаше Каноничното име при влизане ...или
нещо такова
Току-що го пробвах, но за съжаление не става '<img'> Благодаря все пак!

Иначе разгледах файловете в директорията /var/log/, за да разбера къде горе-долу се крие грешката и открих нещо : всеки път, когато се опитвам да се логна в Managment Console, в логовете намирам :

Примерен код
/var/log/httpd/access_lo - - [08/Jan/2008:19:45:26 +0200] "GET /admin-serv/authenticate HTTP/1.0" 400 294 "-" "Fedora-Management-Console/1.1.0"

Примерен код

[Tue Jan 08 19:45:26 2008] [error] [client] Client sent malformed Host header

Като че ли /admin-serv/authenticate създава проблеми.


Свободата не се подарява - тя се извоюва с много труд и пот.


Подобни теми
Заглавие Започната от Отговора Прегледи Последна публикация
executible directory
Настройка на програми
sunhater 3 1238 Последна публикация Nov 24, 2003, 22:39
от sunhater
active directory
ddantgwyn 0 1600 Последна публикация Jun 08, 2004, 18:04
от ddantgwyn
Игнориране на Parent Directory
Настройка на програми
zeridon 1 1252 Последна публикация Mar 08, 2005, 22:43
от zeridon
Защо при инсталл ми дава NO SUCH FILE OR DIRECTORY
Настройка на програми
suse_linux 10 2160 Последна публикация Feb 16, 2006, 19:28
от GoodT
Fedora Core 4 & Windows Server мрежа
Настройка на хардуер
Sambutcha 5 2242 Последна публикация Feb 24, 2006, 23:02
от sdr