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@xxxxxxxx> 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.
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).You will need to look at slapd-lanldap2/logs/errors - there should be some clue there.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 . . .The directory /opt/fedora-ds/slapd-lanldap2/logs exists, but is empty.
Then, run start-setup with a high debug level e.g. start-slapd -d 1If 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.
This doesn't work. setup is not idempotent. You will have to remove your installation and reinstall.I terminated setup and rerun it. Now I got: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/serverNo 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#
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users