restarting the dbus system service

jyunker · 11-04-2014, 02:59 PM

I tried to run the command in my Centos 6.5, 64 bit system

parted /dev/sda 'print'

and the output was

** ERROR ** This program cannpt start until you start the dbus system service

aborting...
Aborted

So I learned the way I thought that I could start the dbus system service
which was:

service messagebus restart

but when I ran that command I got the command

** ERROR ** This program cannpt start until you start the dbus system service

aborting...
Aborted

So how to I start the dbus system service? I cannot run anything until I started the dbus system service.

R,

jyunker

ferrari · 11-04-2014, 09:07 PM

Can you simply start it with the following?

Code:

service messagebus start

Check the status with

Code:

chkconfig messagebus

If necessary do

Code:

chkconfig messagebus on

jyunker · 11-05-2014, 08:34 AM

Thanks very much. i will try it.

R,

jyunker

jyunker · 11-05-2014, 03:37 PM

Okay, service start gives the response:

service messagebus start
sh: service command not found

chkconfig messagebus gives

sh: /sbin/runlevel : No such file or directory

chkconfig messagebus on
give no response at all.

but simply typing chkconfig

chkconfig

gives

Code:

abrtd            0:off   1:off  2:off  3:on  4:off  5:on  6:off     
std              0:off   1:off  2:off  3:on  4:on   5:on  6:off     
audtd            0:off   1:off  2:on   3:on  4:on   5:off 6:off   
avahi-daemon     0:off   1:off  2:off  3:on  4:on   5:on  6:off 
centrify-kcm     0:off   1:off  2:on   3:on  4:on   5:off 6:off 
centrify-sshd    0:off   1:off  2:on   3:on  4:on   5:off 6:off 
centrifyda       0:off   1:off  2:on   3:on  4:on   5:off 6:off 
centrifydc       0:off   1:off  2:on   3:on  4:on   5:off 6:off 
dropbox          0:off   1:off  2:on   3:on  4:on   5:off 6:off 
irqbalance       0:off   1:off  2:on   3:on  4:on   5:off 6:off 
jexec            0:on    1:on   2:off  3:on  4:on   5:on  6:off
messagebus       0:off   1:off  2:on   3:on  4:on   5:on  6:off 
portreserve      0:off   1:off  2:on   3:on  4:on   5:off 6:off 
psacct           0:off   1:off  2:off  3:on  4:on   5:off 6:off  
qemu-ga          0:off   1:off  2:on   3:on  4:on   5:on  6:off 
sanlock          0:off   1:off  2:on   3:on  4:on   5:on  6:off 
wdaemon          0:off   1:off  2:off  3:off 4:off  5:off 6:off 
wlmd             0:off   1:off  2:on   3:on  4:on   5:on  6:off

If I copied them down correctly.

There is no fsck on my system, but there is fsck.ext2 in /sbin which I presume is for files of ext2 type only.

There is also an fack.ext3, fsck.ext4 and fsck.extdev all in the sbin directory.

What they are is the equivalent og fsck, but for specific files.

Are these last statements correct?

Please guide me on the next step.

Any help appreciated.

R,

jyunker

ferrari · 11-05-2014, 04:39 PM

Assuming you're at runlevel 2,3,4, or 5 messagebus is set to be active

Code:

messagebus       0:off   1:off  2:on   3:on  4:on   5:on  6:off

You could always check that the daemon is running

Code:

ps -A|grep dbus

ferrari · 11-05-2014, 04:43 PM

Quote:

There is no fsck on my system, but there is fsck.ext2 in /sbin which I presume is for files of ext2 type only.

There is also an fack.ext3, fsck.ext4 and fsck.extdev all in the sbin directory.

Refer to 'man fsck'

http://linux.die.net/man/8/fsck

Quote:

What they are is the equivalent og fsck, but for specific files.

No, specific partition types.