boot message log where?

vladuz976 · 2008-12-13 10:47:31

Hi,
I am getting some Dbus [Failed] message on boot when the daemons are started.

I did searched /var/log/ very carefully for anything containing 'Dbus' but in vain.
dmesg doesn't return anything either.
It simply scrolls by so fast that I couldn't possible read it or make any use out of that information.

Shouldn't there be a simple way to log these messages?
They do seem important.

Thank you,

tomk · 2008-12-13 11:29:42

Even if they were logged, you would still just see Dbus [Failed] - that's the output the init script provides. If it's failing, it's because the command that the init script executes is failing - in this case, /usr/bin/dbus-daemon --system. Run that command as root in a terminal, and check for error messages.

Xauthority · 2008-12-13 15:58:22

I would like to have this as a feature, I mean the output somewhere in /var/log of the content displayed in /dev/tty0 at bootup.
The reason is that I have installed a fresh install of arch via pacman -r into /arch2 on a reiserFS (3.6) partition.
At bootup there is showing up some permission error with /etc/rc.d/functions and the output {done} {fail} {busy} is not coloured.
I could only see a little part of the message because its quite fast and dmesg | grep functions has no result.
Help would be greatly appreciated.
PS: it looked like yhe error appears because the FS is in ro mode but at that step in my ext3 install
everything works fine and it looks like (it should be though) its also ro at that time.

EDIT: Just wanted to say that everything else work OK.

Last edited by Xauthority (2008-12-13 16:00:17)

patroclo7 · 2008-12-13 18:35:30

It should be easy to edit the /etc/rc.d/functions initscript so that the ouput goes in a file.

phrakture · 2008-12-13 22:49:03

Or just change your /etc/issue so it doesn't clear the screen...

vladuz976 · 2008-12-14 02:57:57

Phrakture,

you're right, it would only tell me the same thing in the log. The problem is that it says something more than just Dbus failed. There are about 3 lines of output and it is simply too fast. I am sure reading that output would give me a good hint as to where to look to fix it.

Xauthority · 2008-12-14 06:50:59

phrakture wrote:

Or just change your /etc/issue so it doesn't clear the screen...

My problem is not that the screen get cleared, (well, my issue file is empty) the message is at the beginning before running the
daemons and at the end I have my login and above this the daemon {done} and {bkrg} status messages. I tried with a vga parameter at boot so with
the higher resolution I may see the problem, but it was still too small.

patroclo7 wrote:

It should be easy to edit the /etc/rc.d/functions initscript so that the ouput goes in a file.

Yeah that was the 1st thing I tried but I didnt get it

EDIT: fixed a typo

Last edited by Xauthority (2008-12-14 14:33:49)

pointone · 2008-12-14 17:12:56

Hitting your "Scroll Lock" key will pause the boot process, giving you time to read.

Xauthority · 2008-12-14 17:32:03

pointone wrote:

Hitting your "Scroll Lock" key will pause the boot process, giving you time to read.

wow thanks for the hint, first time I hear of this (OMG)
Now if I could know
How to edit the /etc/rc.d/functions initscript so that the ouput goes in a file, I would be really happy.

Last edited by Xauthority (2008-12-14 17:32:20)

Arch Linux

#1 2008-12-13 10:47:31

boot message log where?

#2 2008-12-13 11:29:42

Re: boot message log where?

#3 2008-12-13 15:58:22

Re: boot message log where?

#4 2008-12-13 18:35:30

Re: boot message log where?

#5 2008-12-13 22:49:03

Re: boot message log where?

#6 2008-12-14 02:57:57

Re: boot message log where?

#7 2008-12-14 06:50:59

Re: boot message log where?

#8 2008-12-14 17:12:56

Re: boot message log where?

#9 2008-12-14 17:32:03

Re: boot message log where?

Board footer