LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Mandriva (https://www.linuxquestions.org/questions/mandriva-30/)
-   -   How to capture boot messages? (https://www.linuxquestions.org/questions/mandriva-30/how-to-capture-boot-messages-685380/)

Torben Friis 11-22-2008 11:04 AM

How to capture boot messages?
 
Hi,
My question is in the header.
best regards
torben friis

amani 11-22-2008 11:10 AM

see the log files in /var
If logging is not enabled, do that

Torben Friis 11-24-2008 06:55 AM

boot logging
 
Quote:

Originally Posted by amani (Post 3350971)
see the log files in /var
If logging is not enabled, do that

Thanks Amani,
How do I enable boot logging (Mandriva 2008)? I can find an empty file /var/log/boot.log and an entry local7.* -> pointing to that file in /etc/syslog.conf, but no explanation on how to do. WWW does'nt help.
regards
torben friis

repo 11-24-2008 08:05 AM

Quote:

How do I enable boot logging (Mandriva 2008)?

# vi /etc/default/bootlogd

You’ll see the following lines:

# Run bootlogd at startup ?
BOOTLOGD_ENABLE=No

Change No to Yes

Torben Friis 11-24-2008 10:27 AM

boot logging
 
Quote:

Originally Posted by repo (Post 3352662)
# vi /etc/default/bootlogd

You’ll see the following lines:

# Run bootlogd at startup ?
BOOTLOGD_ENABLE=No

Change No to Yes

Hi repo,
I had to make the file, but it had no effect. Could it be, since extensive searching www gives no result, that it is not possible to log to boot.log?
regards
torben friis

repo 11-24-2008 10:45 AM

Is bootlogd instlalled ?
Perhaps mandriva doesn't instal it by deault?
Perhaps you can do a search for bootlogd on your system

ernie 11-25-2008 02:22 PM

I use Mandriva 2009.0 here and boot logging is enabled by default in /etc/sysconfig

The boot log file(s) are located at /var/log/boot.log and (at present) four archived log files exist: /var/log/boot.log.1.gz thru /var/log/boot.log.4.gz.

bootlogd is included in the package sysvinit-2.86-8mdv2009.0.x86_64 (on my system). There is also a 32 bit package sysvinit-2.86-8mdv2009.0.i586

HTH,

Torben Friis 11-26-2008 05:34 AM

Quote:

Originally Posted by ernie (Post 3354018)
I use Mandriva 2009.0 here and boot logging is enabled by default in /etc/sysconfig

The boot log file(s) are located at /var/log/boot.log and (at present) four archived log files exist: /var/log/boot.log.1.gz thru /var/log/boot.log.4.gz.

bootlogd is included in the package sysvinit-2.86-8mdv2009.0.x86_64 (on my system). There is also a 32 bit package sysvinit-2.86-8mdv2009.0.i586

HTH,

Thanks repo and ernie,
I found /sbin/bootlogd and ran it and got the message: cannot find console device &"-:1 in /dev.
But I have to install it so it runs when I boot - right?
I have Mandriva 2008 (32 bit), free and there is only /var/log/boot.log
regards
torben

GlennsPref 11-29-2008 12:06 AM

You need to be root to view logs.
 
Hi, to see what your kernel output during boot, type

dmesg |more

To check the errors when x starts, open as text

/home/user-name/.xsession-errors

Cheers, Glenn

<edit>You might need root access to view the log files in /var/log/, depends on security setting (I think).</edit>

Torben Friis 12-02-2008 12:46 PM

Quote:

Originally Posted by GlennsPref (Post 3358397)
Hi, to see what your kernel output during boot, type

dmesg |more

To check the errors when x starts, open as text

/home/user-name/.xsession-errors

Cheers, Glenn

<edit>You might need root access to view the log files in /var/log/, depends on security setting (I think).</edit>

Hi Glenn,
I did not understand .xsession-errors. I now get just one line in boot.log for every boot telling that resolv.conf has been updated.
But if I key Esc and I at a certain point in boot I can step through the boot. Maybe the best.
regards
torben

GlennsPref 12-02-2008 08:34 PM

dmesg is a log file found /vag/log/

piping it to more, a way to view text.

From a shell, or a teminal for the shell from your favourite window manager,

like xterm or konsole.
For long texts you may need to increase the buffer for
konsole to be able to display all the lines, not just the
last bit.

This is how you view the messages captured during (AFTER) boot.

dmesg | more

use the "space" key to scroll down as you read. When it reaches the end it exits.

You can copy and paste from the terminal/shell if you have a GUI. For later reference.

To view the screen errors, if any, type

cat /var/log/Xorg.0.log | grep EE

This will only display lines with EE from the current log.

To view the whole .xsession-errors (it's a hidden-system file)file, type

vim ~/.xsession-errors

use the vi manual to get the key strokes for vi...
Code:

arrows and PageUp PageDown work as normal to navigate
i insert, to insert
esc to exit (all modes) insert mode
:wq to write and quit
:q to quit without writing
! to force command :wq
dd delete line
dw delete word
a enter append mode
e enter edit mode
/ find forwards
:w save

see how you go, Glenn

Torben Friis 12-07-2008 02:48 PM

Quote:

Originally Posted by GlennsPref (Post 3362421)
dmesg is a log file found /vag/log/

piping it to more, a way to view text.

From a shell, or a teminal for the shell from your favourite window manager,

like xterm or konsole.
For long texts you may need to increase the buffer for
konsole to be able to display all the lines, not just the
last bit.

This is how you view the messages captured during (AFTER) boot.

dmesg | more

use the "space" key to scroll down as you read. When it reaches the end it exits.

You can copy and paste from the terminal/shell if you have a GUI. For later reference.

To view the screen errors, if any, type

cat /var/log/Xorg.0.log | grep EE

This will only display lines with EE from the current log.

To view the whole .xsession-errors (it's a hidden-system file)file, type

vim ~/.xsession-errors

use the vi manual to get the key strokes for vi...
Code:

arrows and PageUp PageDown work as normal to navigate
i insert, to insert
esc to exit (all modes) insert mode
:wq to write and quit
:q to quit without writing
! to force command :wq
dd delete line
dw delete word
a enter append mode
e enter edit mode
/ find forwards
:w save

see how you go, Glenn

Hi Glenn,
Thanks very much. That was clear.
best regards
torben

simeon.mattes 11-14-2010 12:22 PM

How is that possible in slackware? There are some log files in /var/log but I would like only one file which has all the boot messages.

simeon.mattes 11-14-2010 01:49 PM

What worked for me, but I don't know if there is a problem with that is:

at the beginning of /etc/rc.d/rc.S

bootlogd -l /var/log/boot/boot.$(date +%Y%m%d.%H%M%S)

This means that all messages will be written in /var/log/boot/boot.yyyymmdd.HHMMSS file


However bootlogd should be installed in your system

catkin 11-14-2010 02:18 PM

Quote:

Originally Posted by simeon.mattes (Post 4158543)
How is that possible in slackware? There are some log files in /var/log but I would like only one file which has all the boot messages.

Summarised in this LQ post. Slackware64 13.1 in a VirtualBox VM does allow Shift+PgUp/PgDn paging of tty1/console but not on real hardware :scratch:


All times are GMT -5. The time now is 12:22 AM.