Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back > Forums > Linux Forums > Linux - Software
User Name
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.


  Search this Thread
Old 11-03-2006, 07:40 AM   #1
Registered: Oct 2006
Posts: 80

Rep: Reputation: 15
Fedora system stuck at system message bus service upon bootup


Problem was started when I installed LDAP server. Then, I restarted pc to effect the changes I made... But, bootup does not work properly. It takes long to start system message bus and seemed like no chance to view the login screen.

How can I fix this? I have used interactive mode inorder to bypass smb to startup but with no luck. The login screen still not showing up.....

Old 10-25-2007, 07:15 AM   #2
LQ Newbie
Registered: Oct 2007
Posts: 1

Rep: Reputation: 0
edit /etc/ldap.conf and add a line

bind_policy soft

# Reconnect policy: hard (default) will retry connecting to

Hope this helps
Old 10-26-2007, 09:54 PM   #3
Registered: Oct 2006
Posts: 80

Original Poster
Rep: Reputation: 15

Wow... Thanks.. I didn't expect I get an answers to this problem. It is already one year since I post this event. I am really appreciate your help.

Thanks once again...
Old 12-06-2007, 12:21 AM   #4
LQ Newbie
Registered: Dec 2007
Posts: 1

Rep: Reputation: 0
Hi iam also facing the same problem,that is linux get stuck while i made some entries in /etc/ldap.conf ..Will the system restart? I saw the solution.How can i edit the file without restaring?
Old 02-16-2009, 01:54 PM   #5
LQ Newbie
Registered: Oct 2006
Distribution: CentOS
Posts: 6

Rep: Reputation: 0
what ultimately resolved this for me was

I found this in centos mantis

In the case of my environment after reviewing the /var/log/messages startups for both system_message bus and NFS stat (rpc.statd) were hanging on connecting to LDAP.

bind_policy soft
to /etc/ldap.conf did help because it forced the system to use the bind_timeout in ldap.conf of 120 seconds.

Lastly though to ultimately resolve the issue I moved my routes from rc.local to a new file S11routes in rc3.d to follow S10network. This allowed the system to have the proper routes so statd and system message bus could find the ldap server.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
FC5- System Stops at "Starting System Message BUS " athreyavc Linux - Hardware 5 08-19-2007 11:46 AM
bus: Can't send to audit system bionicmaximu Linux - General 0 01-15-2006 11:12 PM
Fedora 2 system banner/message Blackout_08 Fedora 6 03-06-2005 10:06 PM
System Bus Speed CoffinDancer Linux - Software 3 01-24-2002 11:59 PM

All times are GMT -5. The time now is 12:34 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration