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@redhat.com ReportedBy: axel.thimm@atrpms.net QAContact: qe-baseos-auto@redhat.com CC: rbulling@pkrinternet.com, tibbs@math.uh.edu, jwilson@redhat.com, oracle@provocation.net, ian@iay.org.uk, ask@develooper.com, loganjerry@gmail.com, jplans@redhat.com, amessina@messinet.com, dqarras@yahoo.com, jsafrane@redhat.com, amcnabb@mcnabbs.org, fedora-triage-list@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.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=484489
--- Comment #1 from Axel Thimm axel.thimm@atrpms.net 2009-02-07 06:47:34 EDT --- The fix was in the /etc/ldap.conf.rpmnew file. Sorry for the noise.
--------------------------
I can't close this as a duplicate of bug #243753, as bugzilla says:
You tried to change the Status field from NEW to CLOSED, but only a user with the required permissions may change that field.
Please press Back and try again.
Can someone with sufficient permissions close this as a duplicate of bug #243753? Thanks!
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=484489
Jose Plans jplans@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |DUPLICATE
--- Comment #2 from Jose Plans jplans@redhat.com 2009-02-07 08:39:11 EDT --- Sure, thanks!
*** This bug has been marked as a duplicate of 243753 ***
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=484489
--- Comment #3 from Jose Plans jplans@redhat.com 2009-02-07 08:39:31 EDT --- Sure, thanks!
triage@lists.fedoraproject.org