Bug 189624 - System boot hangs when ldap authentication is configured and ldap server is down
Summary: System boot hangs when ldap authentication is configured and ldap server is down
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: nss_ldap
Version: 5
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-21 18:44 UTC by Martin Kessler
Modified: 2008-05-06 15:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-05-06 15:49:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Kessler 2006-04-21 18:44:39 UTC
Description of problem:
When FC5 is configured to use ldap and flatfiles for authentication serveral
services hang during boot. E.g. named

Version-Release number of selected component (if applicable):
Any

How reproducible:
Configure system authentication, flat files + ldap .. reboot

Steps to Reproduce:
1. Setup system auth files + ldap
2. Turn off ldap service
3. Reboot
  
Actual results:
Strating Service named waits for resolving group

Expected results:
Should continue as named group is already defined in group file

Additional info:
setting nsswitch 
passwd: files ldap
shadow: files ldap
group: files
 
will fix the boot problem but then ldap won't work properly at the end

Comment 1 Marc Maurer 2006-07-20 11:35:40 UTC
We are seeing/having this problem too, and it's rather annoying.

Another option is to use "bind_policy soft" in /etc/ldap.conf, which will at
least allow the server to boot. 

The problem with this solution however, is that nss_ldap won't try to reconnect
anymore when the ldap server becomes available again.

Comment 2 Bug Zapper 2008-04-04 02:42:53 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
http://fedoraproject.org/wiki/LifeCycle/EOL

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 3 Bug Zapper 2008-05-06 15:49:46 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.