[Bug 484489] New: messagebus fails to start if the system is configured with ldap authentication
bugzilla at redhat.com
bugzilla at redhat.com
Sat Feb 7 09:42:29 UTC 2009
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: messagebus fails to start if the system is configured with ldap authentication
https://bugzilla.redhat.com/show_bug.cgi?id=484489
Summary: messagebus fails to start if the system is configured
with ldap authentication
Product: Red Hat Enterprise Linux 5
Version: 5.3
Platform: All
OS/Version: Linux
Status: NEW
Status Whiteboard: bzcl34nup
Severity: high
Priority: medium
Component: nss_ldap
AssignedTo: nalin at redhat.com
ReportedBy: axel.thimm at atrpms.net
QAContact: qe-baseos-auto at redhat.com
CC: rbulling at pkrinternet.com, tibbs at math.uh.edu,
jwilson at redhat.com, oracle at provocation.net,
ian at iay.org.uk, ask at develooper.com,
loganjerry at gmail.com, jplans at redhat.com,
amessina at messinet.com, dqarras at yahoo.com,
jsafrane at redhat.com, amcnabb at mcnabbs.org,
fedora-triage-list at redhat.com
Depends on: 206399
Estimated Hours: 0.0
Classification: Red Hat
Clone Of: 206399
+++ This bug was initially created as a clone of Bug #206399 +++
Description of problem:
The script /etc/init.d/messagebus hangs during bootup if the system is
configured for LDAP authentication. Disabling LDAP authentication solves the
problem.
_____________________________________________________________________
The problems described in the bug above exist in RHEL5 since 5.0.
If the server rebooting is ldap-serving itself, dbus hangs during reboots. In a
debugging session, ensuring that ldap starts before messagebus solved the
issue.
So it either needs a reordering of the boot sequence of the services (e.g. move
ldap to the front of any consuming service), or some nss_ldap magic.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the fedora-triage-list
mailing list