useless@mail.bg
2008-Jan-10 09:59 UTC
[Fedora-directory-users] Fedora Directory Server 1.1 : Cannot log in the Managent Console
Hello!
Several days ago I downloaded and installed Fedora Directory Server
1.1. The problem is that I cannot log in the Management Console
(fedora-idm-console)- every time when I try to log in it(
http://img181.imageshack.us/my.php?image=snapshot1bx4.png ), I get the
following error :
http://img108.imageshack.us/my.php?image=snapshot2fi1.png
and I find the following messages in the /var/log/httpd dir:
/var/log/httpd/access_log :
127.0.0.1 - - [08/Jan/2008:19:45:26 +0200] "GET
/admin-serv/authenticate HTTP/1.0" 400 294 "-"
"Fedora-Management-Console/1.1.0"
/var/log/httpd/error_log :
[Tue Jan 08 19:45:26 2008] [error] [client 127.0.0.1] Client sent
malformed Host header
The dirsrv, dirsrv-admin and httpd deamons are running. I have no
problem with opening localhost:9830 and
localhost:9830/admin-serv/authenticate in my browser.
Here are the settings that I entered during the install (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 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.
[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
environment.
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
<hostname>.<domainname>
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 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.
[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''
------------------------------------------------------
------------------------------------------------------
[General]
AdminDomain = localdomain
SuiteSpotGroup = fdsuser
ConfigDirectoryLdapURL = ldap://localhost.localdomain:389/o=NetscapeRoot
ConfigDirectoryAdminID = admin
SuiteSpotUserID = fdsuser
ConfigDirectoryAdminPwd = <pass>
FullMachineName = localhost.localdomain
[admin]
ServerAdminID = admin
ServerAdminPwd = <pass>
SysUser = fdsuser
Port = 9830
[slapd]
InstallLdifFile = suggest
ServerIdentifier = localhost
ServerPort = 389
AddOrgEntries = Yes
RootDN = cn=Directory Manager
RootDNPwd = <pass>
SlapdConfigForMC = yes
Suffix = dc=localdomain
UseExistingMC = 0
AddSampleEntries = No
------------------------------------------------------
------------------------------------------------------
Any ideas why I cannot log in the Management Console?
Thanks in advance!
-------------------------------------
Sportingbet.com
Залози на живо на всички срещи от Шампионска Лига!
http://bg.sportingbet.com/t/index.aspx?affiliate=mailbg10
Rich Megginson
2008-Jan-10 17:33 UTC
Re: [Fedora-directory-users] Fedora Directory Server 1.1 : Cannot log in the Managent Console
useless@mail.bg wrote:> Hello! > > Several days ago I downloaded and installed Fedora Directory Server 1.1.What platform? Which Java are you using? fedora-idm-console -D 9 -f console.log may provide more information.> The problem is that I cannot log in the Management Console > (fedora-idm-console)- every time when I try to log in it( > http://img181.imageshack.us/my.php?image=snapshot1bx4.png ), I get the > following error : > > http://img108.imageshack.us/my.php?image=snapshot2fi1.png > > and I find the following messages in the /var/log/httpd dir: > > /var/log/httpd/access_log : > 127.0.0.1 - - [08/Jan/2008:19:45:26 +0200] "GET > /admin-serv/authenticate HTTP/1.0" 400 294 "-" > "Fedora-Management-Console/1.1.0" > > /var/log/httpd/error_log : > [Tue Jan 08 19:45:26 2008] [error] [client 127.0.0.1] Client sent > malformed Host headerThis is very strange. The admin server should be using /var/log/dirsrv/admin-serv for its logs. You should not have the operating system apache running and listening to the same port number (9830) as the admin server, if you have them both running at the same time. grep Listen /etc/httpd/conf/httpd.conf grep Listen /etc/dirsrv/admin-serv/console.conf The console cannot talk to standard apache - the admin server has special configuration and a special apache module that allows it to communicate with the console.> > The dirsrv, dirsrv-admin and httpd deamons are running. I have no > problem with opening localhost:9830 and > localhost:9830/admin-serv/authenticate in my browser.Does "localhost" resolve to the same thing as "localhost.localdomain"? Try doing fedora-idm-console -A http://localhost:9830/ <snip>
useless@mail.bg
2008-Jan-10 20:40 UTC
Re: [Fedora-directory-users] Fedora Directory Server 1.1 : Cannot log in the Management Console
I am running Fedora 8. The version of java is 1.5.0. I am sorry for not mentioning that. This is the output of the command /FEDORA-IDM-CONSOLE -D 9 -F CONSOLE.LOG :/ (the file /console.log/ is empty after quiting the Managment Console Log-in window) ------------------------- java.util.prefs.userRoot=/root/.fedora-idm-console path.separator=: java.vm.name=GNU libgcj java.vm.specification.name=Java(tm) Virtual Machine Specification java.runtime.version=1.5.0 java.util.prefs.systemRoot=/root/.fedora-idm-console java.home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre java.vm.specification.version=1.0 line.separator java.vm.specification.vendor=Sun Microsystems Inc. gnu.classpath.home.url=file:///usr/lib gnu.gcj.progname=com.netscape.management.client.console.Console gnu.classpath.version=0.93 java.specification.version=1.5 gnu.java.util.zoneinfo.dir=/usr/share/zoneinfo java.library.path=/usr/lib gnu.classpath.vm.shortname=libgcj java.class.version=49.0 java.specification.name=Java(tm) Platform API Specification os.version=2.6.23.9-85.fc8 gnu.classpath.home=/usr user.home=/root file.encoding=UTF-8 os.name=Linux user.name=root java.class.path=/usr/lib/java/jss4.jar:/usr/share/java/ldapjdk.jar:/usr/share/java/idm-console-base.jar:/usr/share/java/idm-console-mcc.jar:/usr/share/java/idm-console-mcc_en.jar:/usr/share/java/idm-console-nmclf.jar:/usr/share/java/idm-console-nmclf_en.jar:/usr/share/java/fedora-idm-console-1.1.0_en.jar java.io.tmpdir=/tmp os.arch=i386 java.fullversion=GNU libgcj 4.1.2 20070925 (Red Hat 4.1.2-33) user.language=bg java.specification.vendor=Sun Microsystems Inc. user.dir=/root java.vm.info=GNU libgcj 4.1.2 20070925 (Red Hat 4.1.2-33) java.version=1.5.0 java.ext.dirs=/usr/share/java/ext sun.boot.class.path=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre/lib/rt.jar gnu.gcj.user.realname=root java.vm.vendor=Free Software Foundation, Inc. java.vendor.url=http://gcc.gnu.org/java/ java.vendor=Free Software Foundation, Inc. file.separator=/ java.vm.version=4.1.2 20070925 (Red Hat 4.1.2-33) http.agent=gnu-classpath/0.93 (libgcj/4.1.2 20070925 (Red Hat 4.1.2-33)) gnu.gcj.precompiled.db.path=/usr/lib/gcj-4.1.2/classmap.db gnu.cpu.endian=little user.region=BG gnu.gcj.runtime.endorsed.dirs=/usr/share/java/gcj-endorsed Fedora-Management-Console/1.1.0 B2007.354.1015 RemoteImage: NOT found in cache loader368512:com/netscape/management/nmclf/icons/Error.gif RemoteImage: Create RemoteImage cache for loader368512 RemoteImage: NOT found in cache loader368512:com/netscape/management/nmclf/icons/Inform.gif RemoteImage: NOT found in cache loader368512:com/netscape/management/nmclf/icons/Warn.gif RemoteImage: NOT found in cache loader368512:com/netscape/management/nmclf/icons/Question.gif ResourceSet: NOT found in cache loader368512:com.netscape.management.client.components.components RemoteImage: NOT found in cache loader368512:com/netscape/management/client/theme/images/logo16.gif RemoteImage: NOT found in cache loader368512:com/netscape/management/client/theme/images/login.gif ResourceSet: NOT found in cache loader368512:com.netscape.management.client.util.default ResourceSet: found in cache loader368512:com.netscape.management.client.util.default ResourceSet: found in cache loader368512:com.netscape.management.client.util.default HERE I ENTER USERID, PASSWORD AND ADMINISTRATION URL. CommManager> New CommRecord (http:/admin-serv/authenticate) ResourceSet: found in cache loader368512:com.netscape.management.client.theme.theme http://:80/[0:0] open> Ready http://:80/[0:0] accept> http:/admin-serv/authenticate http://:80/[0:0] send> GET http://:80/[0:0] send> /admin-serv/authenticate http://:80/[0:0] send> HTTP/1.0 http://:80/[0:0] send> Host: :80 http://:80/[0:0] send> Connection: Keep-Alive http://:80/[0:0] send> User-Agent: Fedora-Management-Console/1.1.0 http://:80/[0:0] send> Accept-Language: en http://:80/[0:0] send> Authorization: Basic http://:80/[0:0] send> YWRtaW46ZmVkMHJh http://:80/[0:0] send> http://:80/[0:0] send> http://:80/[0:0] recv> HTTP/1.1 400 Bad Request http://:80/[0:0] error> HttpException: Response: HTTP/1.1 400 Bad Request Status: 400 URL: http:/admin-serv/authenticate http://:80/[0:0] close> Closed ------------------------- // // / GREP LISTEN /ETC/HTTPD/CONF/HTTPD.CONF/ returns Listen 80 / GREP LISTEN /ETC/DIRSRV/ADMIN-SERV/CONSOLE.CONF/ returns # Listen: Allows you to bind Apache to specific IP addresses and/or # Change this to Listen on specific IP addresses as shown below to # e.g. "Listen 12.34.56.78:80" # To allow connections to IPv6 addresses add "Listen [::]:80" Listen 0.0.0.0:9830 "localhost" resolves to the same thing as "localhost.localdomain" - 127.0.0.1 When I run the command /FEDORA-IDM-CONSOLE -A HTTP://LOCALHOST:9830// , the situation is absolutely the same as when I excecute only /FEDORA-IDM-CONSOLE/ - the same error message appear when I click on the "OK" button ( http://img108.imageshack.us/my.php?image=snapshot2fi1.png[1] ). Thank you for the time spent to help me! Links: ------ [1] http://img108.imageshack.us/my.php?image=snapshot2fi1.png ------------------------------------- Sportingbet.com Залози на живо на всички срещи от Шампионска Лига! http://bg.sportingbet.com/t/index.aspx?affiliate=mailbg10
Rich Megginson
2008-Jan-10 20:51 UTC
Re: [Fedora-directory-users] Fedora Directory Server 1.1 : Cannot log in the Management Console
useless@mail.bg wrote:> I am running Fedora 8. The version of java is 1.5.0. I am sorry for > not mentioning that.This will not work. You must use the IcedTea Java on Fedora 8. yum install java-1.7.0-icedtea Then use java -version to confirm that is the correct one.> > This is the output of the command */fedora-idm-console -D 9 -f > console.log :/* (the file /console.log/ is empty after quiting the > Managment Console Log-in window) > > ------------------------------------------------------------------------ > > /java.util.prefs.userRoot=/root/.fedora-idm-console > path.separator=: > java.vm.name=GNU libgcj > java.vm.specification.name=Java(tm) Virtual Machine Specification > java.runtime.version=1.5.0 > java.util.prefs.systemRoot=/root/.fedora-idm-console > java.home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre > / >This means you''re using gcj 1.5, not icedtea java.> > /java.vm.specification.version=1.0 > line.separator> > / ><snip>> > /http://:80/[0:0] send> Host: :80 > / >This looks like some sort of bug in the gcj url parser - it should be localhost:9830, not ":80". icedtea java should not have this problem.> > /http://:80/[0:0] send> Connection: Keep-Alive > http://:80/[0:0] send> User-Agent: Fedora-Management-Console/1.1.0 > http://:80/[0:0] send> Accept-Language: en > http://:80/[0:0] send> Authorization: Basic > http://:80/[0:0] send> YWRtaW46ZmVkMHJh > http://:80/[0:0] send> > http://:80/[0:0] send> > http://:80/[0:0] recv> HTTP/1.1 400 Bad Request > http://:80/[0:0] error> HttpException: > Response: HTTP/1.1 400 Bad Request > Status: 400 > URL: http:/admin-serv/authenticate > http://:80/[0:0] close> Closed/ > > ------------------------------------------------------------------------ > > /*grep Listen /etc/httpd/conf/httpd.conf*/ returns/ > Listen 80/ > > /*grep Listen /etc/dirsrv/admin-serv/console.conf*/ returns > /# Listen: Allows you to bind Apache to specific IP addresses and/or > # Change this to Listen on specific IP addresses as shown below to > # e.g. "Listen 12.34.56.78:80" > # To allow connections to IPv6 addresses add "Listen [::]:80" > Listen 0.0.0.0:9830/ > > "localhost" resolves to the same thing as "localhost.localdomain" - > 127.0.0.1 > > When I run the command */fedora-idm-console -A > http://localhost:9830//* , the situation is absolutely the same as > when I excecute only */fedora-idm-console/* - the same error message > appear when I click on the "OK" button ( > http://img108.imageshack.us/my.php?image=snapshot2fi1.png ). > > Thank you for the time spent to help me! > > > > ------------------------------------- > Sportingbet.com > Залози на живо на всички срещи от Шампионска Лига! > <http://mail.bg/ads/www/delivery/ck.php?oaparams=2__bannerid=308__zoneid=17__cb=7211ba1a87__maxdest=http://bg.sportingbet.com/t/index.aspx?affiliate=mailbg10> > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users >
useless@mail.bg
2008-Jan-10 22:20 UTC
Re: [Fedora-directory-users] Fedora Directory Server 1.1 : Cannot log in the Management Console (Solved)
> This will not work. You must use the IcedTea Java on Fedora 8. > yum install java-1.7.0-icedtea > Then use java -version to confirm that is the correct one.This solved the problem! Thanks a lot! ------------------------------------- Powered by Mail.BG - http://mail.bg