Red Hat Bugzilla – Bug 450515
dbus dies right after start on system start
Last modified: 2015-10-05 07:55:37 EDT
Description of problem:
When the messagebus dbus-daemon is started on the system start it immediately
dies (but give state OK on the boot screen). That leaves to the problem that
hald cannot be started and so several tools depending on HAL are broken.
Starting the stuff AFTER the boot works well.
Version-Release number of selected component (if applicable):
Boot the system.
No dbus-daemon is running (and so no hald also).
It should work.
I tried to debug the stuff. Unfortunately dbus-daemon do log many thinks (=
NULL) to any logfile. So I cannot see what kind of problems the daemon have.
Also stracing do not work as with a running strace the daemon runs fine.
I'm experiencing the same problem, also with version 1.0.0-7.el5. Is there a
workaround? Starting dbus and hald after boot does not avoid problems with the
GNOME settings daemon.
We've got this one too. Anyone know of a workaround.
This isn't for the feint of heart, but it has been working for me for about a
day and a half.
1: Rename /bin/dbus-daemon to /bin/dbus-daemon-real
2: Create a new file named /bin/dbus-daemon with the following contents (be
sure not to indent anything).
strace -o /dev/null /bin/dbus-daemon-real $*
3: Don't forget to set the ownership and permissions appropriately.
4: Reboot. haldaemon should start normally.
Oh, and this won't work if selinux is being strict.
eek, bit of a grim work around. I'm surprised this issue isn't huge, we are now
getting complaints from users who are seeing, CD's and USB's not mounting
I'm now wondering is there something different in my (and your) setup that we
are seeing this.
I'm using a Dell Precision 670 with hyperthreading turned off (I believe).
This machine has two CPUs (two chips, one core each).
Wild guess: it has something to do with multiple processors. strace is slowing
things down enough to avoid some kind of race condition.
My present work around is putting into /etc/rc.local
Seems to be OK at starting later in the boot process. Not sure why this would
stop a race condition, if that is the problem.
This seems to be related to bug #448014. I downgraded to nss_ldap-253-5.el5 and
this seems to have gone now. I'll relate this bug to it if others see this same
Unless the original poster or the follow ups are seeing this still, I'd suggest this is a duplicate of bug #448014, which when nss_ldap was fixed this problem went away.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
I don't know why I got nagged by that kind of bugs. I also cannot help if you need that long to react on bug reports.