Christopher Waltham wrote: > Hi Prabhat, > > On Nov 14, 2008, at 2:16 PM, Prabhat Ranjan Pradhan wrote: > >> Hi Chris and all, >> >> I too struggled for the same problem for almost 4 months. I googled >> several times to find any solution. >> >> At last I discovered a link Posted by Pieter de Rijk >> <http://blog.adslweb.net/serendipity/authors/1-Pieter-de-Rijk> . I >> must say thanks to this gentleman who did a splendid job to pinpoint >> the error. >> >> >> getting hint from this link what I did is: >> >> 1. disabled SELinux >> 2. created a user (and default group) fedora-ds >> 3. installed fedora-ds using yum. >> 4. changed the ownership of /var/run/dirsrv to fedora-ds >> # chwon -R fedora-ds:fedora-ds /var/run/dirsrv >> 5. started installation with setup-ds-admin.pl. >> 6. entered fedora-ds as user and group name when prompted by the >> installer.. >> 7. Hurray!!! my installation was successfull. >> >> I had repeated this procedure several times on vmware virtual >> machines runing fedora9 and fedora8. > > Thanks for the note! I'm using VMware ESX so I'm taking snapshots to > make troubleshooting easier. > > I didn't realize SELinux was still enabled, so I disabled it. Then I > followed the rest of your instructions, but I still had problems: > > Are you ready to set up your servers? [yes]: > Creating directory server . . . > Your new DS instance 'ldap' was successfully created. > Creating the configuration directory server . . . > The suffix 'o=NetscapeRoot' already exists. Config entry DN > 'cn="o=NetscapeRoot",cn=mapping tree,cn=config'. > > That's using fedora-ds as both user and group. Curiously, if I do a > chmod/chown and set /var/run/dirsrv to to nobody:nobody (and then > choose the "nobody" user in setup-ds-admin.pl), I get exactly the same > problem... This looks like a different problem. This is what usually happens if you run setup again without having first cleaned up everything from the prior run. One problem with setup-ds-admin.pl is that you cannot simply run it again - it will detect the previous configuration (however broken it may be). > > > Chris > >> >> >> >> May I bring this issue to the notice of development team that the >> file permission of /var/run/dirsrv is an issue to be looked into. >> The authentic reason for this can be fond in Mr Pieter de Rijk >> <http://blog.adslweb.net/serendipity/authors/1-Pieter-de-Rijk>'s >> work. at >> http://blog.adslweb.net/serendipity/article/244/Fedora-directory-server >> >> Prabhat >> >> >> >> >> On Fri, Nov 14, 2008 at 8:13 PM, Christopher Waltham >> <cwaltham at bowdoin.edu <mailto:cwaltham at bowdoin.edu>> wrote: >> >> I'm using RHEL5.2 (i386) and installing RPMs from the FDS >> repository that's mentioned on the FDS wiki. But I'm having >> trouble configuring FDS 1.1.3 due to errors that I believe are >> related to permissions on /var/run/dirsrv. >> >> Before installing DS, here are the permission on /var/run/dirsrv: >> >> [root at falls ~]# ls -ald /var/run/dirsrv >> drwxr-xr-x 3 root root 4096 Nov 14 09:24 /var/run/dirsrv >> >> When finishing the end of setup-ds-admin.pl, I see these messages: >> >> Are you ready to set up your servers? [yes]: >> Creating directory server . . . >> Server failed to start !!! Please check errors log for problems >> Possible timeout starting server: timeout=1226673415 now=1226673416 >> Could not start the directory server using command >> '/usr/lib/dirsrv/slapd-falls/start-slapd'. The last line from >> the error log was '[14/Nov/2008:09:26:55 -0500] - >> Fedora-Directory/1.1.3 B2008.269.157 starting up >> '. Error: Unknown error 256 >> Error: Could not create directory server instance 'falls'. >> Exiting . . . >> Log file is '/tmp/setupblsNWZ.log' >> >> There is nothing else of relevance in either /tmp/setupblsNWZ.log >> or /var/log/dirsrv/slapd-falls/errors >> >> If I try and start the directory server after the installation >> failed, I get this error: >> >> [root at falls ~]# /etc/init.d/dirsrv start >> Starting dirsrv: >> falls... [FAILED] >> *** Warning: 1 instance(s) failed to start >> >> If I manually chmod & chown the /var/run/dirsrv directory, it >> will start: >> >> [root at falls ~]# chmod 770 /var/run/dirsrv && chown nobody:nobody >> /var/run/dirsrv >> [root at falls ~]# /etc/init.d/dirsrv start >> Starting dirsrv: >> falls... [ OK ] >> >> However, because the setup-ds-admin.pl process never completed, >> the admin server hasn't been configured (and I don't want to have >> to do that by hand). Note that I am using nobody:nobody in the >> FDS installer when asked who I want to run the services as. >> >> When I manually ( chmod 770 /var/run/dirsrv && chown >> nobody:nobody /var/run/dirsrv ) *before* I run setup-ds-admin.pl >> I get this error: >> >> [08/11/14:09:00:33] - [Setup] Info Are you ready to set up your >> servers? >> [08/11/14:09:00:34] - [Setup] Info yes >> [08/11/14:09:00:34] - [Setup] Info Creating directory server . . . >> [08/11/14:09:00:36] - [Setup] Info Your new DS instance 'ldap' >> was successfully created. >> [08/11/14:09:00:36] - [Setup] Info Creating the configuration >> directory server . . . >> [08/11/14:09:00:36] - [Setup] Fatal The suffix 'o=NetscapeRoot' >> already exists. Config entry DN 'cn="o=NetscapeRoot",cn=mapping >> tree,cn=config'. >> >> [08/11/14:09:00:36] - [Setup] Fatal Failed to create the >> configuration directory server >> [08/11/14:09:00:36] - [Setup] Fatal Exiting . . . >> >> Any thoughts? This is getting pretty frustrating :-\ >> >> Thanks, >> >> >> Chris >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> <mailto:Fedora-directory-users at redhat.com> >> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> <mailto:Fedora-directory-users at redhat.com> >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3258 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.fedoraproject.org/pipermail/389-users/attachments/20081114/fbbbf585/attachment.bin
