[SOLVED] [FAIL] Message During Boot...dbus, hal, rpc bind

jeff story · 2009-10-02 10:52:28

My Arch with Gnome desktop is working great, no noticeable problems. However, during reboot or startup, I see [FAIL] messages scroll by.
I finally decided to research these messages. I used scroll lock to get the following details.

Starting d-bus system messagebus [BUSY]

Failed to start message bus: The PID file /var/run/dbus.pid exists, if the message bus is not running, remove this file.

Starting hardware abstraction layer [FAIL]

Starting RPC bind [FAIL]

I've added and am using networkmanager if this has anything to do with the fail messages.

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE:US/Pacific
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(fuse vboxdrv)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="Arch2009p2"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
INTERFACES=(!eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng networkmanager dbus hal netfs nfs-common nfs-server crond  rpcbind fam avahi-daemon stbd  autofs sshd)
#

Last edited by jeff story (2009-10-02 11:56:31)

arkham · 2009-10-02 11:01:11

Maybe networkmanager requires dbus? Try removing dbus from the daemons array. If else fails, remove the pid file by hand.

Surgat_ · 2009-10-02 11:03:04

There might not be related, but networkmanager should be started after hal. Also, dbus is started by hal, so there is no need to put it in DAEMONS.

http://wiki.archlinux.org/index.php/Net … it_daemons

jeff story · 2009-10-02 11:55:45

Thanks,

A little daemons order and tweaking solved it!!!

DAEMONS=(syslog-ng !network hal networkmanager netfs nfs-common nfs-server crond @rpcbind fam avahi-daemon stbd @autofs sshd)

Arch Linux

#1 2009-10-02 10:52:28

[SOLVED] [FAIL] Message During Boot...dbus, hal, rpc bind

#2 2009-10-02 11:01:11

Re: [SOLVED] [FAIL] Message During Boot...dbus, hal, rpc bind

#3 2009-10-02 11:03:04

Re: [SOLVED] [FAIL] Message During Boot...dbus, hal, rpc bind

#4 2009-10-02 11:55:45

Re: [SOLVED] [FAIL] Message During Boot...dbus, hal, rpc bind

Board footer