Fedora directory users - Feb 2009 - Fedora DS startup problem

Hi,

I recently installed Fedora DS 1.1.3 on my system and ran the
setup-ds-admin script with no problems.  Everything worked very
well--until I rebooted!

Upon reboot, the directory server refused to start.  Below are the
relevant lines from the /dirsrv/slapd-host/errors file:
02/Feb/2009:00:11:33 -0600] - Waiting for 4 database threads to stop
[02/Feb/2009:00:11:33 -0600] - All database threads now stopped
[02/Feb/2009:00:11:33 -0600] - slapd stopped.
[02/Feb/2009:00:12:51 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
starting up
[02/Feb/2009:00:13:56 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
starting up
[02/Feb/2009:00:14:02 -0600] - slapd started.  Listening on All Interfaces
port 389 for LDAP requests
[02/Feb/2009:00:14:24 -0600] - slapd shutting down - signaling operation
threads
[02/Feb/2009:00:14:24 -0600] - slapd shutting down - closing down internal
subsystems and plugins
[02/Feb/2009:00:14:29 -0600] - Waiting for 4 database threads to stop
[02/Feb/2009:00:14:30 -0600] - All database threads now stopped
[02/Feb/2009:00:14:30 -0600] - slapd stopped.
[02/Feb/2009:00:16:07 -0600] - Shutting down due to possible conflicts
with other slapd processes
[02/Feb/2009:00:20:11 -0600] - Shutting down due to possible conflicts
with other slapd processes

And it continues to print "Shutting down due to possible conflicts with
other slapd processes" every single time I try to start the directory
server.  No other messages are printed to the error log, all permissions
are OK, and the directory admin server starts with no problem.

Befuddled, I tried re-running the setup-ds-admin script.  Again, the
directory server came online and worked perfectly upon completion of that
script, but it failed upon reboot as before.

There are no other LDAP servers running on this machine.  A process scan
showed no slapd processes running, and the LDAP port does not have a
process glommed onto it.

Any assistance you can provide would be appreciated!

Thank you,

Timothy Pearson
Raptor Engineering

Hi 

Is there anything else that runs on port 389 om your machine?

Per


On 2/2/09 8:22 AM, "kb9vqf@pearsoncomputing.net"
<kb9vqf@pearsoncomputing.net> wrote:
> And it continues to print "Shutting down due to possible conflicts
with
> other slapd processes" every single time I try to start the directory
> server.  No other messages are printed to the error log, all permissions
> are OK, and the directory admin server starts with no problem.
> 
> Befuddled, I tried re-running the setup-ds-admin script.  Again, the
> directory server came online and worked perfectly upon completion of that
> script, but it failed upon reboot as before.

> Hi
>
> Is there anything else that runs on port 389 om your machine?
>
> Per
>
>
No, there is not.  fuser confirms this:

root@odin:~# fuser -n tcp 389
root@odin:~# /etc/init.d/dirsrv start
 * Starting FDS instances : ...                                           
                                                                         
                              * odin ...                                 
                                                                         
                                                            *  error     
                                                                         
                                                                         
                * *** Warning: 1 instance(s) failed to start...          
                                                                         
                                      [fail]
root@odin:~# fuser -n tcp 389
root@odin:~#

Tim

kb9vqf@pearsoncomputing.net wrote:
> Hi,
>
> I recently installed Fedora DS 1.1.3 on my system and ran the
> setup-ds-admin script with no problems.  Everything worked very
> well--until I rebooted!
>
> Upon reboot, the directory server refused to start.  Below are the
> relevant lines from the /dirsrv/slapd-host/errors file:
> 02/Feb/2009:00:11:33 -0600] - Waiting for 4 database threads to stop
> [02/Feb/2009:00:11:33 -0600] - All database threads now stopped
> [02/Feb/2009:00:11:33 -0600] - slapd stopped.
> [02/Feb/2009:00:12:51 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
> starting up
> [02/Feb/2009:00:13:56 -0600] - Fedora-Directory/1.1.3 B2009.031.2025
> starting up
> [02/Feb/2009:00:14:02 -0600] - slapd started.  Listening on All Interfaces
> port 389 for LDAP requests
> [02/Feb/2009:00:14:24 -0600] - slapd shutting down - signaling operation
> threads
> [02/Feb/2009:00:14:24 -0600] - slapd shutting down - closing down internal
> subsystems and plugins
> [02/Feb/2009:00:14:29 -0600] - Waiting for 4 database threads to stop
> [02/Feb/2009:00:14:30 -0600] - All database threads now stopped
> [02/Feb/2009:00:14:30 -0600] - slapd stopped.
> [02/Feb/2009:00:16:07 -0600] - Shutting down due to possible conflicts
> with other slapd processes
> [02/Feb/2009:00:20:11 -0600] - Shutting down due to possible conflicts
> with other slapd processes
>
> And it continues to print "Shutting down due to possible conflicts
with
> other slapd processes" every single time I try to start the directory
> server.  No other messages are printed to the error log, all permissions
> are OK, and the directory admin server starts with no problem.
>
> Befuddled, I tried re-running the setup-ds-admin script.
> Again, the
> directory server came online and worked perfectly upon completion of that
> script, but it failed upon reboot as before.
>
> There are no other LDAP servers running on this machine.  A process scan
> showed no slapd processes running, and the LDAP port does not have a
> process glommed onto it.
>
> Any assistance you can provide would be appreciated!
>   
Do have any problems if you manually start the server?
What happens if you do
 service dirsrv start
or
 service dirsrv restart
?
> Thank you,
>
> Timothy Pearson
> Raptor Engineering
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

> kb9vqf@pearsoncomputing.net wrote:
> Do have any problems if you manually start the server?
> What happens if you do
>  service dirsrv start
> or
>  service dirsrv restart
> ?
>
Yes--that is what I have been referring to all along is manual start of
the server through that method.

I have even tried executing the slapd-start command from within the
slapd-<hostname> directory, and every single time it comes up with a
generic error on screen and "Shutting down due to possible conflicts with
other slapd processes" in the log.

kb9vqf@pearsoncomputing.net wrote:
>> kb9vqf@pearsoncomputing.net wrote:
>>     
>
>   
>> Do have any problems if you manually start the server?
>> What happens if you do
>>  service dirsrv start
>> or
>>  service dirsrv restart
>> ?
>>
>>     
>
> Yes--that is what I have been referring to all along is manual start of
> the server through that method.
>
> I have even tried executing the slapd-start command from within the
> slapd-<hostname> directory, and every single time it comes up with a
> generic error on screen and "Shutting down due to possible conflicts
with
> other slapd processes" in the log.
>   
Ok - try this - /usr/lib/dirsrv/slapd-yourinstance/start-slapd -d
1
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

> kb9vqf@pearsoncomputing.net wrote:
> Ok - try this - /usr/lib/dirsrv/slapd-yourinstance/start-slapd -d 1
Thank you for the -d 1 option--dirsrv finally told me what is wrong:
Error - Problem accessing the lockfile /var/lock/dirsrv/slapd-odin/lock
[02/Feb/2009:12:56:53 -0600] - Shutting down due to possible conflicts
with other slapd processes

Sure beats 8 hours of trial and error...

Tim