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



Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

--
Fedora-directory-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-directory-users

Reply via email to