Fedora directory users - Dec 2005 - setup fails, cannot start server (slapd)

After successfully building (with dsbuild) and installing FDS on a SLES 9
system, the startup script hangs.

I have run /opt/fedora-ds/setup/setup with default-answers to all
questions (besides the password ;-) ). The problems are:

	Fedora Directory Server system tuning analysis version 04-APRIL-2005.

	NOTICE : System is i686-unknown-linux2.6.5-7.201-smp (2 processors).

	ERROR: We support kernel version 2.4.7 and higher.

	Continue? (yes/no) 
        
Looks like a string compare bug to me. I typed "yes".
Then, some questions later, I got the infinitive loop:

	[slapd-lanldap2]: starting up server ...
	[slapd-lanldap2]: Attempting to obtain server status . . .
	[slapd-lanldap2]: Attempting to obtain server status . . .
	[slapd-lanldap2]: Attempting to obtain server status . . .
	...

I terminated setup and rerun it. Now I got:

	In order to reconfigure your installation, the Configuration Directory
	Administrator password is required.  Here is your current information:

	Configuration Directory:
	Configuration Administrator ID:

	At the prompt, please enter the password for the Configuration Administrator.

	Fedora configuration directory server
	administrator ID: admin
	Password: xxxxxxxx
        
        
	Could not connect to f8/LC_CTYPE
	Press any key to continue.


What now? 
I found no hint in http://directory.fedora.redhat.com/wiki/FAQ or 
http://directory.fedora.redhat.com/wiki/Install_Guide


-- 
-- Ullrich Horlacher, BelWue Coordination ------- mailto:framstag@belwue.de --
   Computing Centre Universitaet Stuttgart (RUS)   
   Allmandring 30, 70550 Stuttgart, Germany          fax: +49 711 678 8363
-- saft://saft.belwue.de/framstag ----------------- http://www.belwue.de/ ----

Ulli Horlacher wrote:
>After successfully building (with dsbuild) and installing FDS on a SLES 9
>system, the startup script hangs.
>  
>
Earlier you posted that you were having problems building on SLES 10:
>I have no fix for this problem. libgssapi_krb5 is missing on SLES, the
>free kerberos implementation heimdal does not contain a libgssapi_krb5
>
>What now?
>
I guess SLES 9 has the correct kerberos/gssapi packages, but not SLES 10?
>I have run /opt/fedora-ds/setup/setup with default-answers to all
>questions (besides the password ;-) ). The problems are:
>
>	Fedora Directory Server system tuning analysis version 04-APRIL-2005.
>
>	NOTICE : System is i686-unknown-linux2.6.5-7.201-smp (2 processors).
>
>	ERROR: We support kernel version 2.4.7 and higher.
>
>	Continue? (yes/no) 
>        
>Looks like a string compare bug to me. I typed "yes".
>  
>
Yes.  There is no support in dsktune for SLES, so you can just ignore that.
>Then, some questions later, I got the infinitive loop:
>
>	[slapd-lanldap2]: starting up server ...
>	[slapd-lanldap2]: Attempting to obtain server status . . .
>	[slapd-lanldap2]: Attempting to obtain server status . . .
>	[slapd-lanldap2]: Attempting to obtain server status . . .
>  
>
You will need to look at slapd-lanldap2/logs/errors - there should be 
some clue there.
>	...
>
>I terminated setup and rerun it. Now I got:
>  
>
This doesn''t work.  setup is not idempotent.  You will have to remove 
your installation and reinstall.  But the real key is to find out why 
the server did not start.  Also look for core files in 
slapd-lanldap2/logs or bin/slapd/server
>	In order to reconfigure your installation, the Configuration Directory
>	Administrator password is required.  Here is your current information:
>
>	Configuration Directory:
>	Configuration Administrator ID:
>
>	At the prompt, please enter the password for the Configuration
Administrator.
>
>	Fedora configuration directory server
>	administrator ID: admin
>	Password: xxxxxxxx
>        
>        
>	Could not connect to f8/LC_CTYPE
>	Press any key to continue.
>
>
>What now? 
>I found no hint in http://directory.fedora.redhat.com/wiki/FAQ or 
>http://directory.fedora.redhat.com/wiki/Install_Guide
>
>
>  
>

On Tue 2005-12-20 (10:15), Richard Megginson wrote:
> >After successfully building (with dsbuild) and installing FDS on a SLES
9
> >system, the startup script hangs.
> 
> Earlier you posted that you were having problems building on SLES 10:
No, Daniel Spannbauer <ds@marco.de> has problems with SuSE 10.0.
I am using SLES 9.

> >I have no fix for this problem. libgssapi_krb5 is missing on SLES, the
> >free kerberos implementation heimdal does not contain a libgssapi_krb5
> >
> >What now?
> 
> I guess SLES 9 has the correct kerberos/gssapi packages, but not SLES 10?
I solved this problem by copying the libgssapi_krb5 and companion libs
from SuSE 3.3 to my SLES 9 into /usr/local/lib (a rpm-based installation
was not possible due to version conflicts with other packages).

With this I was able to run dsbuild sucessfully. I have now FDS RPMs for
SLES 9:
-rw-r--r-- framstag users         28.833.422 2005-12-19 12:59:53
dsbuild/ds/ldapserver/work/fedora-ds-1.0.1-1.Linux.i586.opt.rpm
-rw-r--r-- framstag users            793.310 2005-12-19 11:58:52
dsbuild/ds/setuputil/work/12.19/fedora-setuputil-devel-1.0-1.Linux2.6.i586.opt.rpm


> >Then, some questions later, I got the infinitive loop:
> >
> >	[slapd-lanldap2]: starting up server ...
> >	[slapd-lanldap2]: Attempting to obtain server status . . .
> >	[slapd-lanldap2]: Attempting to obtain server status . . .
> >	[slapd-lanldap2]: Attempting to obtain server status . . .
> >  
> >
> 
> You will need to look at slapd-lanldap2/logs/errors - there should be 
> some clue there.
The directory /opt/fedora-ds/slapd-lanldap2/logs exists, but is empty.

> >I terminated setup and rerun it. Now I got:
> 
> This doesn''t work.  setup is not idempotent.  You will have to
remove
> your installation and reinstall.  
Good to know :-)
One should add this to the FAQ or Installation Guide.


> But the real key is to find out why the server did not start.  Also look
> for core files in slapd-lanldap2/logs or bin/slapd/server
No core-dumps:

lanldap2:/opt/fedora-ds# find . | grep core
./bin/slapd/install/schema/00core.ldif
./setup/svrcore
./setup/svrcore/svrcore.inf
./slapd-lanldap2/config/schema/00core.ldif
lanldap2:/opt/fedora-ds#



-- 
-- Ullrich Horlacher, BelWue Coordination ------- mailto:framstag@belwue.de --
   Computing Centre Universitaet Stuttgart (RUS)   
   Allmandring 30, 70550 Stuttgart, Germany          fax: +49 711 678 8363
-- saft://saft.belwue.de/framstag ----------------- http://www.belwue.de/ ----

Ulli Horlacher wrote:
>On Tue 2005-12-20 (10:15), Richard Megginson wrote:
>
>  
>
>>>After successfully building (with dsbuild) and installing FDS on a
SLES 9
>>>system, the startup script hangs.
>>>      
>>>
>>Earlier you posted that you were having problems building on SLES 10:
>>    
>>
>
>No, Daniel Spannbauer <ds@marco.de> has problems with SuSE 10.0.
>I am using SLES 9.
>  
>
Oh, sorry.
>
>  
>
>>>I have no fix for this problem. libgssapi_krb5 is missing on SLES,
the
>>>free kerberos implementation heimdal does not contain a
libgssapi_krb5
>>>
>>>What now?
>>>      
>>>
>>I guess SLES 9 has the correct kerberos/gssapi packages, but not SLES
10?
>>    
>>
>
>I solved this problem by copying the libgssapi_krb5 and companion libs
>from SuSE 3.3 to my SLES 9 into /usr/local/lib (a rpm-based installation
>was not possible due to version conflicts with other packages).
>
>With this I was able to run dsbuild sucessfully. I have now FDS RPMs for
>SLES 9:
>-rw-r--r-- framstag users         28.833.422 2005-12-19 12:59:53
dsbuild/ds/ldapserver/work/fedora-ds-1.0.1-1.Linux.i586.opt.rpm
>-rw-r--r-- framstag users            793.310 2005-12-19 11:58:52
dsbuild/ds/setuputil/work/12.19/fedora-setuputil-devel-1.0-1.Linux2.6.i586.opt.rpm
>  
>
Ok.
>
>
>  
>
>>>Then, some questions later, I got the infinitive loop:
>>>
>>>	[slapd-lanldap2]: starting up server ...
>>>	[slapd-lanldap2]: Attempting to obtain server status . . .
>>>	[slapd-lanldap2]: Attempting to obtain server status . . .
>>>	[slapd-lanldap2]: Attempting to obtain server status . . .
>>> 
>>>
>>>      
>>>
>>You will need to look at slapd-lanldap2/logs/errors - there should be 
>>some clue there.
>>    
>>
>
>The directory /opt/fedora-ds/slapd-lanldap2/logs exists, but is empty.
>  
>
So, no server, and no core.  I guess the next thing to do is when you 
get to this point, go ahead and break setup (just Ctrl-C).
Then, run start-setup with a high debug level e.g. start-slapd -d 1
If you don''t get any useful information from level 1, you can use -d 
131071 to get an enormous amount of output.  That should give us some 
clues as to why the server is not starting.
>
>  
>
>>>I terminated setup and rerun it. Now I got:
>>>      
>>>
>>This doesn''t work.  setup is not idempotent.  You will have to
remove
>>your installation and reinstall.  
>>    
>>
>
>Good to know :-)
>One should add this to the FAQ or Installation Guide.
>  
>
Ok.
>
>
>  
>
>>But the real key is to find out why the server did not start.  Also look
>>for core files in slapd-lanldap2/logs or bin/slapd/server
>>    
>>
>
>No core-dumps:
>
>lanldap2:/opt/fedora-ds# find . | grep core
>./bin/slapd/install/schema/00core.ldif
>./setup/svrcore
>./setup/svrcore/svrcore.inf
>./slapd-lanldap2/config/schema/00core.ldif
>lanldap2:/opt/fedora-ds#
>
>
>
>  
>

On Wed 2005-12-21 (07:44), Richard Megginson wrote:
> So, no server, and no core.  I guess the next thing to do is when you 
> get to this point, go ahead and break setup (just Ctrl-C).
Ok.

> Then, run start-setup with a high debug level e.g. start-slapd -d 1
Sorry, but there is neither start-setup nor start-slapd:

lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-setup
lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-slapd
lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-
/opt/fedora-ds/java/html/en/start-console.html
/opt/fedora-ds/java/html/start-console.html
/opt/fedora-ds/setup/adminserver-start-admin.patch
/opt/fedora-ds/shared/config/template/restart-admin.tmpl
/opt/fedora-ds/shared/config/template/start-admin.tmpl



-- 
-- Ullrich Horlacher, BelWue Coordination ------- mailto:framstag@belwue.de --
   Computing Centre Universitaet Stuttgart (RUS)   
   Allmandring 30, 70550 Stuttgart, Germany          fax: +49 711 678 8363
-- saft://saft.belwue.de/framstag ----------------- http://www.belwue.de/ ----

Strange.  That means setup is failing pretty early in the post install 
process.  I assume you are installing from RPM.  Take a look at the 
setup log file.  If you break setup, it should be in /tmp/logXXXXX where 
XXXXX are some random chars.

If that still shows nothing, then I''m not really sure what else to do, 
except debug postinstall.  If you take a look at line 509 in the 
/opt/fedora-ds/setup/setup shell script, that''s the command that runs 
the ns-update shell script.  You can probably do a set -xv in that shell 
script.  That shell script in turn runs ds_create which creates and 
starts the initial directory server instance.  You will need to edit 
ns-update to run ds_create under strace, or possibly even gdb.

Ulli Horlacher wrote:
>On Wed 2005-12-21 (07:44), Richard Megginson wrote:
>
>  
>
>>So, no server, and no core.  I guess the next thing to do is when you 
>>get to this point, go ahead and break setup (just Ctrl-C).
>>    
>>
>
>Ok.
>
>
>  
>
>>Then, run start-setup with a high debug level e.g. start-slapd -d 1
>>    
>>
>
>Sorry, but there is neither start-setup nor start-slapd:
>
>lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-setup
>lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-slapd
>lanldap2:/opt/src# find /opt/fedora-ds/ | grep start-
>/opt/fedora-ds/java/html/en/start-console.html
>/opt/fedora-ds/java/html/start-console.html
>/opt/fedora-ds/setup/adminserver-start-admin.patch
>/opt/fedora-ds/shared/config/template/restart-admin.tmpl
>/opt/fedora-ds/shared/config/template/start-admin.tmpl
>
>
>
>  
>

I''m looking for a way for fds to do 1 of a couple of things;
1. auto increment uid''s and gid''s (I saw this on the wish
list, but wasn''t
sure if this has been implemented yet)
2. If number 1 isn''t yet possible, is there an easy way to display a
list
of used uid and gid''s?  I will need to maintain this list myself, as I
don''t want any duplication here; It would most ideal if it were
possible
to view this info from the users and groups tab view from the console; if
this isn''t possible, perhaps someone can tell me what syntax to use
from
the command line to generate this list?  Thanks very much.  Aaron

Aaron Bliss wrote:
>I''m looking for a way for fds to do 1 of a couple of things;
>1. auto increment uid''s and gid''s (I saw this on the wish
list, but wasn''t
>sure if this has been implemented yet)
>  
>
No, not yet.  Would be pretty easy if you didn''t care what the uid and 
gid were and you were using single master replication.
>2. If number 1 isn''t yet possible, is there an easy way to display
a list
>of used uid and gid''s?  I will need to maintain this list myself,
as I
>don''t want any duplication here; It would most ideal if it were
possible
>to view this info from the users and groups tab view from the console; if
>this isn''t possible, perhaps someone can tell me what syntax to use
from
>the command line to generate this list?  Thanks very much.  Aaron
>  
>
ldapsearch -b dc=your,dc=suffix "objectclass=posixAccount" uidNumber |
grep -v \^dn | grep -v \^\$ | sed -e ''s/uidNumber: //g'' | sort
-n | tail
>--
>Fedora-directory-users mailing list
>Fedora-directory-users@redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>  
>

On Wed 2005-12-21 (10:58), Richard Megginson wrote:
> Strange.  That means setup is failing pretty early in the post install 
> process. 
If I understand you correctly, start-setup and start-slapd are scripts
which will be generated by startup/startup?


> I assume you are installing from RPM.
Yes, I have installed 
dsbuild/ds/ldapserver/work/fedora-ds-1.0.1-1.Linux.i586.opt.rpm
which was generated by my dsbuild-run.
BTW: do I need
dsbuild/ds/setuputil/work/12.19/fedora-setuputil-devel-1.0-1.Linux2.6.i586.opt.rpm
too? I have not installed it yet.

> Take a look at the setup log file.  If you break setup, it should be in
> /tmp/logXXXXX where XXXXX are some random chars.
Yes, I saw them already. I am afraid it contains no usefull info:

(skipping license text)
Do you accept the license terms? (yes/no) y
======================================================================          
Fedora Directory Server 1.0
======================================================================
The Fedora Directory Server is subject to the terms detailed in the
license agreement file called LICENSE.txt.

Late-breaking news and information on the Fedora Directory Server is
available at the following location:

    http://directory.fedora.redhat.com
Continue? (yes/no) y
Fedora Directory Server system tuning analysis version 04-APRIL-2005.

NOTICE : System is i686-unknown-linux2.6.5-7.201-smp (2 processors).

ERROR: We support kernel version 2.4.7 and higher.

NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
(120 minutes).  This may cause temporary server congestion from lost
client connections.

ERROR  : The above errors MUST be corrected before proceeding.

Continue? (yes/no) y
Please select 1, 2, or 3 (default: 2)
getFQDN: hostname = lanldap2
getFQDN: host lanldap2 = lanldap2.rus.uni-stuttgart.de
getFQDN: host lanldap2 has length 9
getFQDN: new max host lanldap2 has length 9
getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
getFQDN: new max host lanldap2.rus.uni-stuttgart.de has length 30
getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
getFQDN: host lanldap2 has length 9

Hostname to use (default: lanldap2.rus.uni-stuttgart.de)
Server user ID to use (default: nobody)
Server group ID to use (default: nobody)
[slapd-lanldap2]: starting up server ...
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .



-- 
-- Ullrich Horlacher, BelWue Coordination ------- mailto:framstag@belwue.de --
   Universitaet Stuttgart
   Allmandring 3a, 70550 Stuttgart, Germany          fax: +49 711 678 8363
-- saft://saft.belwue.de/framstag ----------------- http://www.belwue.de/ ----

Ulli Horlacher wrote:
>On Wed 2005-12-21 (10:58), Richard Megginson wrote:
>  
>
>>Strange.  That means setup is failing pretty early in the post install 
>>process. 
>>    
>>
>
>If I understand you correctly, start-setup and start-slapd are scripts
>which will be generated by startup/startup?
>  
>
Yes.
>
>
>  
>
>>I assume you are installing from RPM.
>>    
>>
>
>Yes, I have installed 
>dsbuild/ds/ldapserver/work/fedora-ds-1.0.1-1.Linux.i586.opt.rpm
>which was generated by my dsbuild-run.
>BTW: do I need
>dsbuild/ds/setuputil/work/12.19/fedora-setuputil-devel-1.0-1.Linux2.6.i586.opt.rpm
>too? I have not installed it yet.
>  
>
No.   You need only fedora-ds-1.0.1-1.Linux.i586.opt.rpm
>
>  
>
>>Take a look at the setup log file.  If you break setup, it should be in
>>/tmp/logXXXXX where XXXXX are some random chars.
>>    
>>
>
>Yes, I saw them already. I am afraid it contains no usefull info:
>
>(skipping license text)
>Do you accept the license terms? (yes/no) y
>======================================================================>  
Fedora Directory Server 1.0
>======================================================================>
>The Fedora Directory Server is subject to the terms detailed in the
>license agreement file called LICENSE.txt.
>
>Late-breaking news and information on the Fedora Directory Server is
>available at the following location:
>
>    http://directory.fedora.redhat.com
>Continue? (yes/no) y
>Fedora Directory Server system tuning analysis version 04-APRIL-2005.
>
>NOTICE : System is i686-unknown-linux2.6.5-7.201-smp (2 processors).
>
>ERROR: We support kernel version 2.4.7 and higher.
>
>NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds
>(120 minutes).  This may cause temporary server congestion from lost
>client connections.
>
>ERROR  : The above errors MUST be corrected before proceeding.
>
>Continue? (yes/no) y
>Please select 1, 2, or 3 (default: 2)
>getFQDN: hostname = lanldap2
>getFQDN: host lanldap2 = lanldap2.rus.uni-stuttgart.de
>getFQDN: host lanldap2 has length 9
>getFQDN: new max host lanldap2 has length 9
>getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
>getFQDN: new max host lanldap2.rus.uni-stuttgart.de has length 30
>getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
>getFQDN: host lanldap2 has length 9
>
>Hostname to use (default: lanldap2.rus.uni-stuttgart.de)
>Server user ID to use (default: nobody)
>Server group ID to use (default: nobody)
>  
>
It should have asked you many more questions here - about other aspects 
of server configuration.  If it didn''t, then something is really wrong
-
it''s skipping all of the configuration steps, which would cause many 
problems.  Are you starting from scratch when you attempt to run setup 
again?  That is, do you
rpm -e fedora-ds
then
rm -rf /opt/fedora-ds
?  Or are you just doing rpm -U fedora-ds-1.0.1 ..., then running setup 
again?  That would cause setup to think you are trying to reconfigure or 
upgrade an existing instance rather than trying to setup your initial 
instance.

But that wouldn''t explain why it failed the very first time, when 
/opt/fedora-ds did not exist.
>[slapd-lanldap2]: starting up server ...
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>
>
>
>  
>

On Thu 2005-12-22 (08:04), Richard Megginson wrote:
> >If I understand you correctly, start-setup and start-slapd are scripts
> >which will be generated by startup/startup?
> 
> Yes.
Nice to know that I have understood at least SOMETHING :-)

> >Continue? (yes/no) y
> >Please select 1, 2, or 3 (default: 2)
> >getFQDN: hostname = lanldap2
> >getFQDN: host lanldap2 = lanldap2.rus.uni-stuttgart.de
> >getFQDN: host lanldap2 has length 9
> >getFQDN: new max host lanldap2 has length 9
> >getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
> >getFQDN: new max host lanldap2.rus.uni-stuttgart.de has length 30
> >getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
> >getFQDN: host lanldap2 has length 9
> >
> >Hostname to use (default: lanldap2.rus.uni-stuttgart.de)
> >Server user ID to use (default: nobody)
> >Server group ID to use (default: nobody)
> >  
> >
> 
> It should have asked you many more questions here - about other aspects 
> of server configuration.  
Yes I was asked many more questions:

Fedora configuration directory server? [No]: 
Do you want to use another directory to store your data? [No]: 
Directory server network port [389]: 
Directory server identifier [lanldap2]: 
administrator ID [admin]: 
Suffix [dc=rus, dc=uni-stuttgart, dc=de]: 
Directory Manager DN [cn=Directory Manager]: 
Administration Domain [rus.uni-stuttgart.de]: 
Administration port [47328]: 
Run Administration Server as [root]: 
Apache Directory [/usr/sbin/]: 

I confirmed all defaults (besides the password, of course) and then I got:

[slapd-lanldap2]: starting up server ...
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .
[slapd-lanldap2]: Attempting to obtain server status . . .


These other questions from above are not found in the log-file.

> problems.  Are you starting from scratch when you attempt to run setup 
> again?  That is, do you
> rpm -e fedora-ds
> then
> rm -rf /opt/fedora-ds
> ?
Yes.


I could now have a closer look (sh -x) at the setup-script, but I will use
another approach: I have now installed fedora core 4 in vmware. 
I will later go back debugging FDS on SLES 9. 
My boss wants a running LDAP server NOW :-}

-- 
-- Ullrich Horlacher, BelWue Coordination ------- mailto:framstag@belwue.de --
   Universitaet Stuttgart
   Allmandring 3a, 70550 Stuttgart, Germany          fax: +49 711 678 8363
-- saft://saft.belwue.de/framstag ----------------- http://www.belwue.de/ ----

Ulli Horlacher wrote:
>On Thu 2005-12-22 (08:04), Richard Megginson wrote:
>
>  
>
>>>If I understand you correctly, start-setup and start-slapd are
scripts
>>>which will be generated by startup/startup?
>>>      
>>>
>>Yes.
>>    
>>
>
>Nice to know that I have understood at least SOMETHING :-)
>  
>
Yes.  It''s not intuitive if you are familiar setting up OpenLDAP and 
other FOSS server software.
>>>Continue? (yes/no) y
>>>Please select 1, 2, or 3 (default: 2)
>>>getFQDN: hostname = lanldap2
>>>getFQDN: host lanldap2 = lanldap2.rus.uni-stuttgart.de
>>>getFQDN: host lanldap2 has length 9
>>>getFQDN: new max host lanldap2 has length 9
>>>getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
>>>getFQDN: new max host lanldap2.rus.uni-stuttgart.de has length 30
>>>getFQDN: host lanldap2.rus.uni-stuttgart.de has length 30
>>>getFQDN: host lanldap2 has length 9
>>>
>>>Hostname to use (default: lanldap2.rus.uni-stuttgart.de)
>>>Server user ID to use (default: nobody)
>>>Server group ID to use (default: nobody)
>>> 
>>>
>>>      
>>>
>>It should have asked you many more questions here - about other aspects 
>>of server configuration.  
>>    
>>
>
>Yes I was asked many more questions:
>
>Fedora configuration directory server? [No]: 
>Do you want to use another directory to store your data? [No]: 
>Directory server network port [389]: 
>Directory server identifier [lanldap2]: 
>administrator ID [admin]: 
>Suffix [dc=rus, dc=uni-stuttgart, dc=de]: 
>Directory Manager DN [cn=Directory Manager]: 
>Administration Domain [rus.uni-stuttgart.de]: 
>Administration port [47328]: 
>Run Administration Server as [root]: 
>Apache Directory [/usr/sbin/]: 
>
>I confirmed all defaults (besides the password, of course) and then I got:
>
>[slapd-lanldap2]: starting up server ...
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>[slapd-lanldap2]: Attempting to obtain server status . . .
>
>
>These other questions from above are not found in the log-file.
>  
>
Ok.  I just wanted to make sure that was not a problem.
>
>  
>
>>problems.  Are you starting from scratch when you attempt to run setup 
>>again?  That is, do you
>>rpm -e fedora-ds
>>then
>>rm -rf /opt/fedora-ds
>>?
>>    
>>
>
>Yes.
>
>
>I could now have a closer look (sh -x) at the setup-script, but I will use
>another approach: I have now installed fedora core 4 in vmware. 
>I will later go back debugging FDS on SLES 9. 
>My boss wants a running LDAP server NOW :-}
>  
>
Sorry about that.  It''s just that we''ve never tried to build
or run it
on SLES.  I''m afraid you are the first person to step up and actually 
try it.