After going through the wizard and choosing "typical" setup, accepting all defaults (except providing a unique FQDN hostname whenever asked), I can't start the console as advised, when the wizard finishes:

[root@foo ~]# cd /opt/fedora-ds/
[root@foo fedora-ds]# ./startconsole -u admin -a http://foo.bar.com:56980/
GC Warning: Out of Memory! Returning NIL!
Exception in thread "main" GC Warning: Out of Memory! Returning NIL!
java.awt.AWTError: Cannot load AWT toolkit: gnu.java.awt.peer.gtk.GtkToolkit
*** Got java.lang.OutOfMemoryError while trying to print stack trace.
[root@foo fedora-ds]# free
total used free shared buffers cached
Mem: 515760 161260 354500 0 23456 114716
-/+ buffers/cache: 23088 492672
Swap: 1048568 0 1048568
[root@foo fedora-ds]#

Note how much free ram there is. The error message happens in about 2 seconds, so there's no way a program can leak memory that fast. Also, it would be nice if the full pathname to a log file was mentioned along with the error message so I could read more verbose info about this error.

totro2:

Thank you for your vigilance! However, I think the particulars in this case are not as you have found. Since version 1.0 of the Fedora DS both the console and the admin server have been open sourced. They are released under the GPL, and should be fully redestributable.

Reference:
http://directory.fedora.redhat.com/wiki/Licensing#Admin_Server_and_Management_Console

totro2:

Also, in case you were not aware, there is a web based administration interface as well. To access it, visit: http://<server>:<adminport>/. The URL is the same as is printed at the end of setup, or used by startconsole. From your previous post, it would be http://foo.bar.com:56980/.

Message was edited by:
telackey

Starting with step 1, to download it you'll need a BitTorrent client. There are several available. This is a very far from complete sampling:

1) Azureus (http://azureus.sourceforge.net)
2) BitComet (http://www.bitcomet.com)
3) Official Client (http://www.bittorrent.com)

I personally prefer Azureus, but they all do the same work, so you can pick the one that suites you best.

Once you've downloaded the appliance, you'll want to make an entry for it in your DNS server. That is because the Directory Server looks up its hostname during its setup. You may be able to skip this step if you have a dynamic DNS server setup.

Next step, make a quick snapshot and then boot the appliance and login as root with a password of "password". You'll be prompted to enter the network configuration info (ie, hostname, IP address, etc.) and then go through the Fedora Directory Server setup.

Here is an example setup:

• Setup Start -----------

Please select the install mode:
1 - Express - minimal questions
2 - Typical - some customization (default)
3 - Custom - lots of customization

Please select 1, 2, or 3 (default: 2) 2

Hostname to use (default: test2.redbudcomputer.local)

Server user ID to use (default: nobody)

Server group ID to use (default: nobody)

…

Do you want to register this software with an existing
Fedora configuration directory server? [No]: No

…

Do you want to use another directory to store your data? [No]: No

…

Directory server network port [389]: 389

…

Directory server identifier [test2]: test2

…

administrator ID [admin]: admin
Password:
Password (again):

…

Suffix [dc=redbudcomputer, dc=local]: dc=redbudcomputer, dc=local

…

Directory Manager DN [cn=Directory Manager]: cn=Directory Manager
Password:
Password (again):

…

Administration Domain [redbudcomputer.local]: redbudcomputer.local

…

Administration port [65342]: 65432

…

Run Administration Server as [root]: root

…

Apache Directory [/usr/sbin/]: /usr/sbin/

…

[slapd-test2]: starting up server ...
[slapd-test2]: Fedora-Directory/1.0.2 B2006.111.2147
[slapd-test2]: test2.redbudcomputer.local:389 (/opt/fedora-ds/slapd-test2)
[slapd-test2]:
[slapd-test2]: [05/Aug/2006:10:23:15 -0400] - Fedora-Directory/1.0.2 B2006.111.2
147 starting up
[slapd-test2]: [05/Aug/2006:10:23:16 -0400] - slapd started. Listening on All I
nterfaces port 389 for LDAP requests
Your new directory server has been started.
Created new Directory Server
Start Slapd Starting Slapd server configuration.
Success Slapd Added Directory Server information to Configuration Server.
Configuring Administration Server...
Setting up Administration Server Instance...
Configuring Administration Tasks in Directory Server...
Configuring Global Parameters in Directory Server...

You can now use the console. Here is the command to use to start the console:
cd /opt/fedora-ds
./startconsole -u admin -a http://test2.redbudcomputer.local:65432/

• Setup End -----------

When the setup is done, open your web browser and point it to the address listed above (in this case, http://test2.redbudcomputer.local:65432/) to begin administering the server. If you’d prefer to use the Java console instead, you’ll need to copy it to another machine or install X in the appliance (eg, ‘yum -y groupinstall "GNOME Desktop Environment"’).

There is a lot to the server, so you’ll want to look into the Fedora documentation page(http://directory.fedora.redhat.com/wiki/Documentation), the Fedora DS Install Guide (http://directory.fedora.redhat.com/wiki/Install_Guide) and best of all the full RedHat documentation (http://www.redhat.com/docs/manuals/dir-server/).

Given that you already have a Fedora Core 5 installation, you might prefer to install the RPMs in that yourself. You can download them from the FDS download page: http://directory.fedora.redhat.com/wiki/Download.

I hope that helps!

I'd like to help, but "doesn't work" is a bit too vague a complaint to admit any help. The best I can do is guess, and ask did you follow the notes in the post above or in the installation summary on the VMTN page and make an entry in your DNS server for the appliance? It must be able to look it up during setup for the LDAP server to start.

Has this issue been resolved?

I also get the "Out of Memory!" error and "Cannot load AWT toolkit..." error when trying to start the console.

The appliance will not download at the moment. Perhaps you can find out why. I tried several times and used two popular bittorrent clients.