HAL daemon cannot be started anymore
 

After some reconfiguration on my FC4-System the haldaemon can no longer be started. Is there a problem with my dbus installation? Does anyone have a guess?

[root@ranatra ~]# service haldaemon start
Starting HAL daemon: [failed]

[root@ranatra ~]# rpm -q --whatprovides /usr/sbin/hald
hal-0.5.2-2

[root@ranatra ~]# ps ax | grep -i dbus
2487 ? Ss 0:00 dbus-daemon-1 --system
3770 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
3773 ? Ss 0:00 dbus-daemon --fork --print-pid 8 --print-address 6 --session
3774 ? S 0:00 /usr/bin/dbus-launch --exit-with-session /etc/X11/xinit/Xclients
4410 pts/0 S+ 0:00 grep -i dbus

[root@ranatra ~]# which dbus-daemon-1
/usr/bin/dbus-daemon-1

[root@ranatra ~]# rpm -q --whatprovides /usr/bin/dbus-daemon-1
dbus-0.22-10

[root@ranatra ~]# rpm -qva | grep -i dbus
dbus-0.33-3.fc4.1
dbus-0.22-10
dbus-glib-0.33-3
dbus-glib-0.33-3.fc4.1
dbus-devel-0.33-3.fc4.1
dbus-0.33-3
dbus-x11-0.33-3.fc4.1
dbus-python-0.33-3.fc4.1

How/why to you have multiple dbus rpms installed????

As root from the console or xterm session remove dbus-0.22-10, dbus-0.33-3 and dbus-glib-0.33-3;
rpm -e dbus-0.22-10 dus-0.33-3 dbus-glib-0.33-3

Removed the packages but still doesn't work (after reboot) :-(

Could be selinux related, try disabling it;

Add selinux=0 to your kernel command line.

Could be messagebus related, check and if needed enabled it;

chkconfig --list messagebus

service messagebus status

selinux is already disabled as it gives problems with the smb-protokoll

[root@ranatra ~]# chkconfig --list messagebus
messagebus 0:off 1:off 2:off 3:on 4:on 5:on 6:off

(Sorry about the emoticons, how can I deactivate them?)

[root@ranatra ~]# service messagebus status
<<no output>>

So, I think messagebus is running ?!

No, it's not if messagebus (dbus) is running the you would see something like;

$ service messagebus status
dbus-daemon-1 (pid 30317 2592) is running...

Do you still have the latest dbus rpms on your system???
If yes, then try reinstalling them;

rpm -Uvh dbus*.rpm --force

Since you already have them installed the use of the '--force' switch is needed.

O.k., reinstalled incl. --force but messagebus is still not running and haldaemon start still fails.

What happens when you (as root) do;

service messagebus restart

If messagebus does start;

service haldaemon restart

Restarting messagebus gives no output. Status request also:

[root@xyz ~]# service messagebus restart
[root@xyz ~]# service messagebus status
[root@xyz ~]#

Very strange, I was expecting to see at least some type of message like;

# service messagebus restart
Stopping system message bus: [FAILED]
Starting system message bus: [ OK ]

or a message that states something along the lines of, system message bus could not be started.

I am at a loss also. Thanks for your help anyway.

You might want to consider making a backup of everything that is of importance to you (system settings, docs, bookmarks, passords and such) and start fresh. Something is not right with the system, could be one of the services is not working right or your missing something of importance to dbus and message bus. Could be a kernel problem like;

http://www.linuxquestions.org/questi...d.php?t=267571

Or something else.

Hal daemon failure
 

I too am having Hal daemon failure. But when I try the mentioned service restart I get the message that the stop failed and the start is OK like in the quote. What do I do at this point?

Check if the smartd service may be causing the problem; /sbin/chkconfig -list smartd

If the service is on then shut it down; service smartd stop
Then try restarting the messagebus service; service messagebus
If it stops and restarts then consider shutting the smartd service off;

/sbin/chkconfig --levels 345 smartd off

I have been having the same problem getting hald to start. Reading the post by Lenard below

# service messagebus restart
Stopping system message bus: [FAILED]
Starting system message bus: [ OK ]

This mean the messagebus was not running becasue it failed to stop it. I found then that afterwards I could start haldaemon /etc/init.d/haldaemon restart

Checking in services under the fedora main menu it showed that messagebus was not checked and wasn't being started on boot. Checking messagebus, saving and rebooting fixed my problem.

Thanks