Fedora directory users - Nov 2008 - "Server failed to start !!!" when installing FDS 1.1.3 in RHEL5.2

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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown nobody:nobody /var/ 
run/dirsrv
[root@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

Christopher Waltham 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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown nobody:nobody 
> /var/run/dirsrv
> [root@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 :-\
Yes.  The first problem caused the second.  The first problem is the 
permissions on /var/run/dirsrv, which allowed you to get past "the point 
of no return" with setup.  That is, your system is already configured to 
the point that subsequent runs of setup think it has been set up correctly.

Try running ds_removal first - you may have to use the -f argument to 
force removal.

Then, try this:
service dirsrv stop # may error if not running - that is ok
service dirsrv-admin stop # may error if not running - that is ok
find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name slapd-\*
If that list looks ok, do
rm -rf `find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name 
slapd-\*`
Finally, rm everything in /etc/dirsrv/admin-serv EXCEPT admserv.conf 
httpd.conf console.conf nss.conf - do not remove these files or the 
directory
Then you should have a clean system to start over with
>
> Thanks,
>
>
> Chris
>
> -- 
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

Thanks for the reply, Rich:

On Nov 14, 2008, at 10:59 AM, Rich Megginson wrote:
>> [root@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody /
>> var/run/dirsrv
>> [root@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 :-\
> Yes.  The first problem caused the second.  The first problem is the  
> permissions on /var/run/dirsrv, which allowed you to get past "the  
> point of no return" with setup.  That is, your system is already  
> configured to the point that subsequent runs of setup think it has  
> been set up correctly.
>
> Try running ds_removal first - you may have to use the -f argument  
> to force removal.
Ok, that''s done.
> Then, try this:
> service dirsrv stop # may error if not running - that is ok
> service dirsrv-admin stop # may error if not running - that is ok
Done.
> find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name slapd-\*
[root@falls sbin]# find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv / 
var -name slapd-\*
/etc/dirsrv/config/slapd-collations.conf
/etc/dirsrv/slapd-falls.removed
find: /usr/lib64: No such file or directory

This is i386, so that looks fine.
> If that list looks ok, do
> rm -rf `find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var - 
> name slapd-\*`
Done...
> Finally, rm everything in /etc/dirsrv/admin-serv EXCEPT admserv.conf  
> httpd.conf console.conf nss.conf - do not remove these files or the  
> directory
Those were the only files in there, so no problem.
> Then you should have a clean system to start over with
Okay, so I can start again with the setup-ds-admin.pl script? And, I  
don''t mean to be rude, but has the root cause of the problem been  
identified? :P I can easily replicate it...


Chris

Christopher Waltham wrote:
> Thanks for the reply, Rich:
>
> On Nov 14, 2008, at 10:59 AM, Rich Megginson wrote:
>
>>> [root@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody
>>> /var/run/dirsrv
>>> [root@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 :-\
>> Yes.  The first problem caused the second.  The first problem is the 
>> permissions on /var/run/dirsrv, which allowed you to get past "the
>> point of no return" with setup.  That is, your system is already 
>> configured to the point that subsequent runs of setup think it has 
>> been set up correctly.
>>
>> Try running ds_removal first - you may have to use the -f argument to 
>> force removal.
>
> Ok, that''s done.
>
>> Then, try this:
>> service dirsrv stop # may error if not running - that is ok
>> service dirsrv-admin stop # may error if not running - that is ok
>
> Done.
>
>> find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name slapd-\*
>
> [root@falls sbin]# find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv 
> /var -name slapd-\*
> /etc/dirsrv/config/slapd-collations.conf
> /etc/dirsrv/slapd-falls.removed
> find: /usr/lib64: No such file or directory
>
> This is i386, so that looks fine.
>
>> If that list looks ok, do
>> rm -rf `find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name 
>> slapd-\*`
>
> Done...
>
>> Finally, rm everything in /etc/dirsrv/admin-serv EXCEPT admserv.conf 
>> httpd.conf console.conf nss.conf - do not remove these files or the 
>> directory
>
> Those were the only files in there, so no problem.
>
>> Then you should have a clean system to start over with
>
> Okay, so I can start again with the setup-ds-admin.pl script?
Yes.
> And, I don''t mean to be rude, but has the root cause of the
problem
> been identified? :P I can easily replicate it...
The root cause is the bogus ownership/permissions on /var/run/dirsrv - 
the directory server user id (default: nobody) must be able to write to 
this directory.  We are working to fix this problem.
>
>
> Chris
>
> -- 
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

On Nov 14, 2008, at 11:32 AM, Rich Megginson wrote:
> Christopher Waltham wrote:
>> Thanks for the reply, Rich:
>>
>> On Nov 14, 2008, at 10:59 AM, Rich Megginson wrote:
>>
>>>> [root@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody /
>>>> var/run/dirsrv
>>>> [root@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 :-\
>>> Yes.  The first problem caused the second.  The first problem is  
>>> the permissions on /var/run/dirsrv, which allowed you to get past  
>>> "the point of no return" with setup.  That is, your
system is
>>> already configured to the point that subsequent runs of setup  
>>> think it has been set up correctly.
>>>
>>> Try running ds_removal first - you may have to use the -f argument
>>> to force removal.
>>
>> Ok, that''s done.
>>
>>> Then, try this:
>>> service dirsrv stop # may error if not running - that is ok
>>> service dirsrv-admin stop # may error if not running - that is ok
>>
>> Done.
>>
>>> find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name  
>>> slapd-\*
>>
>> [root@falls sbin]# find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/ 
>> dirsrv /var -name slapd-\*
>> /etc/dirsrv/config/slapd-collations.conf
>> /etc/dirsrv/slapd-falls.removed
>> find: /usr/lib64: No such file or directory
>>
>> This is i386, so that looks fine.
>>
>>> If that list looks ok, do
>>> rm -rf `find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var - 
>>> name slapd-\*`
>>
>> Done...
>>
>>> Finally, rm everything in /etc/dirsrv/admin-serv EXCEPT  
>>> admserv.conf httpd.conf console.conf nss.conf - do not remove  
>>> these files or the directory
>>
>> Those were the only files in there, so no problem.
>>
>>> Then you should have a clean system to start over with
>>
>> Okay, so I can start again with the setup-ds-admin.pl script?
> Yes.
Hmm, no dice.

Are you ready to set up your servers? [yes]:
Creating directory server . . .
Could not copy file ''/etc/dirsrv/config/slapd-collations.conf''
to ''/
etc/dirsrv/slapd-ldap/slapd-collations.conf''.  Error: No such file or  
directory
Error: Could not create directory server instance ''ldap''.
Exiting . . .
Log file is ''/tmp/setup8I0wbR.log''

[root@falls config]# ls -al /etc/dirsrv/config/
total 24
drwxr-xr-x 2 root root   4096 Nov 14 11:22 .
drwxrwxr-x 7 root nobody 4096 Nov 14 11:31 ..
-rw-r--r-- 1 root root   3595 Sep 24 21:58 certmap.conf
[root@falls config]#

I''m not sure where that file would have gone?


Chris


>
>> And, I don''t mean to be rude, but has the root cause of the
problem
>> been identified? :P I can easily replicate it...
> The root cause is the bogus ownership/permissions on /var/run/dirsrv  
> - the directory server user id (default: nobody) must be able to  
> write to this directory.  We are working to fix this problem.
>>
>>
>> Chris

Christopher Waltham wrote:
> On Nov 14, 2008, at 11:32 AM, Rich Megginson wrote:
>
>> Christopher Waltham wrote:
>>> Thanks for the reply, Rich:
>>>
>>> On Nov 14, 2008, at 10:59 AM, Rich Megginson wrote:
>>>
>>>>> [root@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody
>>>>> /var/run/dirsrv
>>>>> [root@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 :-\
>>>> Yes.  The first problem caused the second.  The first problem
is
>>>> the permissions on /var/run/dirsrv, which allowed you to get
past
>>>> "the point of no return" with setup.  That is, your
system is
>>>> already configured to the point that subsequent runs of setup
think
>>>> it has been set up correctly.
>>>>
>>>> Try running ds_removal first - you may have to use the -f
argument
>>>> to force removal.
>>>
>>> Ok, that''s done.
>>>
>>>> Then, try this:
>>>> service dirsrv stop # may error if not running - that is ok
>>>> service dirsrv-admin stop # may error if not running - that is
ok
>>>
>>> Done.
>>>
>>>> find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var -name
slapd-\*
>>>
>>> [root@falls sbin]# find /etc/dirsrv /usr/lib/dirsrv 
>>> /usr/lib64/dirsrv /var -name slapd-\*
>>> /etc/dirsrv/config/slapd-collations.conf
>>> /etc/dirsrv/slapd-falls.removed
>>> find: /usr/lib64: No such file or directory
>>>
>>> This is i386, so that looks fine.
>>>
>>>> If that list looks ok, do
>>>> rm -rf `find /etc/dirsrv /usr/lib/dirsrv /usr/lib64/dirsrv /var
>>>> -name slapd-\*`
>>>
>>> Done...
>>>
>>>> Finally, rm everything in /etc/dirsrv/admin-serv EXCEPT 
>>>> admserv.conf httpd.conf console.conf nss.conf - do not remove
these
>>>> files or the directory
>>>
>>> Those were the only files in there, so no problem.
>>>
>>>> Then you should have a clean system to start over with
>>>
>>> Okay, so I can start again with the setup-ds-admin.pl script?
>> Yes.
>
> Hmm, no dice.
>
> Are you ready to set up your servers? [yes]:
> Creating directory server . . .
> Could not copy file
''/etc/dirsrv/config/slapd-collations.conf'' to
> ''/etc/dirsrv/slapd-ldap/slapd-collations.conf''.  Error:
No such file
> or directory
> Error: Could not create directory server instance ''ldap''.
> Exiting . . .
> Log file is ''/tmp/setup8I0wbR.log''
>
> [root@falls config]# ls -al /etc/dirsrv/config/
> total 24
> drwxr-xr-x 2 root root   4096 Nov 14 11:22 .
> drwxrwxr-x 7 root nobody 4096 Nov 14 11:31 ..
> -rw-r--r-- 1 root root   3595 Sep 24 21:58 certmap.conf
> [root@falls config]#
>
> I''m not sure where that file would have gone?
You removed it, unfortunately :-(  I neglected to tell you not to remove 
it :-(

For now, unless you need to support different languages, just
touch /etc/dirsrv/config/slapd-collations.conf
before running setup

You can get the real file here - 
http://cvs.fedoraproject.org/viewvc/ldapserver/ldap/schema/slapd-collations.conf?revision=1.6&root=dirsec&view=markup
>
>
> Chris
>
>
>
>>
>>> And, I don''t mean to be rude, but has the root cause of
the problem
>>> been identified? :P I can easily replicate it...
>> The root cause is the bogus ownership/permissions on /var/run/dirsrv 
>> - the directory server user id (default: nobody) must be able to 
>> write to this directory.  We are working to fix this problem.
>>>
>>>
>>> Chris
>
> -- 
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

On Nov 14, 2008, at 11:41 AM, Rich Megginson wrote:
> Christopher Waltham wrote:
>>>>> Okay, so I can start again with the setup-ds-admin.pl
script?
>>> Yes.
>>
>> Hmm, no dice.
>>
>> Are you ready to set up your servers? [yes]:
>> Creating directory server . . .
>> Could not copy file
''/etc/dirsrv/config/slapd-collations.conf'' to ''/
>> etc/dirsrv/slapd-ldap/slapd-collations.conf''.  Error: No such
file
>> or directory
>> Error: Could not create directory server instance
''ldap''.
>> Exiting . . .
>> Log file is ''/tmp/setup8I0wbR.log''
>>
>> [root@falls config]# ls -al /etc/dirsrv/config/
>> total 24
>> drwxr-xr-x 2 root root   4096 Nov 14 11:22 .
>> drwxrwxr-x 7 root nobody 4096 Nov 14 11:31 ..
>> -rw-r--r-- 1 root root   3595 Sep 24 21:58 certmap.conf
>> [root@falls config]#
>>
>> I''m not sure where that file would have gone?
> You removed it, unfortunately :-(  I neglected to tell you not to  
> remove it :-(
LOL, no problem...
> For now, unless you need to support different languages, just
> touch /etc/dirsrv/config/slapd-collations.conf
> before running setup
Thanks! I''ll give that a shot.


Chris

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.


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@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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown nobody:nobody
> /var/run/dirsrv
> [root@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@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

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 . 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...


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''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@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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown nobody:nobody / 
> var/run/dirsrv
> [root@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@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

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@bowdoin.edu <mailto:cwaltham@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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody
>>     /var/run/dirsrv
>>     [root@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@redhat.com
>>     <mailto:Fedora-directory-users@redhat.com>
>>     https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users@redhat.com 
>> <mailto:Fedora-directory-users@redhat.com>
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
> ------------------------------------------------------------------------
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

On Nov 14, 2008, at 6:53 PM, Rich Megginson wrote:
> 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).
That''s what I thought -- and can''t understand. :) This is a
fresh
install of RHEL; I did a find / -name dirsrv and it came up with nada.  
Zero. Zilch! I''m not sure what else to look for?


Chris

Christopher Waltham wrote:
>
> On Nov 14, 2008, at 6:53 PM, Rich Megginson wrote:
>
>> 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).
>
> That''s what I thought -- and can''t understand. :) This is
a fresh
> install of RHEL; I did a find / -name dirsrv and it came up with nada. 
> Zero. Zilch! I''m not sure what else to look for?
No dirsrv directories at all?  There should be some - try rpm -V 
fedora-ds-base - if that has problems, try yum reinstall fedora-ds-base
finally, try setup-ds-admin.pl -ddd to generate debug output - log file 
is in /tmp
>
>
> Chris
>
> -- 
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users

Hi Chris,

I am sorry that I forgot few setps. These have to be performed especially to
install after an unsuccessful attempt.


1. uninstall fedora-ds
    #yum remove fedora-ds
2. remove the following directories.
  # rm -r /etc/dirsrv
 #rm -r /etc/sysconfig/dirsrv
 #rm -r /var/lock/dirsrv
 #rm -r /var/lib/dirsrv


Then follow the steps I had already mentioned to complete your installation.

Hope you will get a clean installation.


Prabhat


On Fri, Nov 14, 2008 at 3:47 PM, Christopher Waltham
<cwaltham@bowdoin.edu>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...
>
>
> 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@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@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@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@falls ~]# chmod 770 /var/run/dirsrv && chown
nobody:nobody
>> /var/run/dirsrv
>> [root@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@redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>
>

On Nov 14, 2008, at 10:45 PM, Rich Megginson wrote:
>>> 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).
>>
>> That''s what I thought -- and can''t understand. :)
This is a fresh
>> install of RHEL; I did a find / -name dirsrv and it came up with  
>> nada. Zero. Zilch! I''m not sure what else to look for?
> No dirsrv directories at all?  There should be some - try rpm -V  
> fedora-ds-base - if that has problems, try yum reinstall fedora-ds- 
> base
> finally, try setup-ds-admin.pl -ddd to generate debug output - log  
> file is in /tmp
Thanks, guys. The problem was this: I was trying to create a new LDAP  
server with the same name (i.e., hostname) as a server that already  
existed on my network. So, the admin server configuration utility was  
freaking out. I played with the /etc/hosts file and now life is good.  
Thanks for the help! Now I have another problem, but I''ll create a new
thread :)


Chris