Why does haldaemon service refuse to start?

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 4
  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6

Issue

  • haldaemon service fails to start
    # service haldaemon start
    Starting HAL daemon:                                       [FAILED]

Resolution

  • One of the reasons haldaemon service will fail to start if the haldaemon user has not been created. Verify that the haldaemon user exists as shown below
    $ grep haldaemon /etc/passwd /etc/shadow /etc/group /etc/gshadow

       /etc/passwd:haldaemon:x:68:68:HAL daemon:/:/sbin/nologin
       /etc/shadow:haldaemon:!!:14572:0:99999:7:::
       /etc/group: haldaemon:x:68:                                              
       /etc/gshadow: haldaemon:x::
  • haldaemon user should be created during hal package installation.This can be manually created using the command below
   $ /usr/sbin/useradd -c 'HAL daemon' -u 68 -s /sbin/nologin -r -d '/' haldaemon

Diagnostic Steps

  • If this fails, we would need "debug" logs to help us identify the issue further
    $ hald --daemon=no --verbose=no 2>&1 | tee /tmp/hal.log

Comment

  • haldaemon service requires messagebus service to run. Please check, if the same is enabled
   $ service messagebus status
   dbus-daemon (pid 1860 1377) is running...

   $ service haldaemon start
  • Component
  • hal

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

3 Comments

Log in to comment
DP Pro 599 points
14 February 2013 9:21 PM

Is this deamon really required on Production server which doesn't run X windows?

Lo Community Member 60 points
19 March 2013 9:45 AM

This was very helpful because @ customer location found out that service haldaemon was not starting because service messagebus not running because in chkconfig messagebus was off @ 6:off

thanks a lot
chandrakant

WC Newbie 5 points
8 July 2014 7:21 PM

[root@ssmd1rhpcg01 ~]# service messagebus status
messagebus (pid 6251) is running...
[root@ssmd1rhpcg01 ~]# chkconfig --list | grep mess
messagebus 0:off 1:off 2:off 3:off 4:off 5:on 6:off