You are not logged in.
Hi all,
my /var/log/boot file is obviously outdated, last entry is saying 'Wed Feb 8 22:03:57 2012...'. As far as I remember I didn't touch system configuration, so I must have missed something. Can anyone give me a short hint how to reanimate bootlogd?
Cheers, Zmann
Last edited by Zmann (2012-06-03 16:59:04)
Offline
My settings for bootlog are in /etc/logrotate.d/bootlog just amend as necessary.
Offline
Hi whompus,
thanks for you reply, but I assume that that in /etc/logrotate.d/bootlog you just configure the logrotate stuff for bootlogd, but my bootlogd doesn't log any more so I assume logrotate isn't helpful here. The bootlogd seems to be okay (I can start it in a shell), but it is no longer started by default since Wed Feb 8. I saw, it is started in /etc/rc.sysinit and that script is mentionned as sysinit script in /etc/inittab. I confess I am confused (is this the new init concept?), so can please anybody shed some light on this mystery and give me a hint what I am expected to do to start bootlogd by default?
Cheers, Zmann
Offline
It should still start. The man page of bootlogd mentions a possible cause, but I'm too much of a linux noob to understand what it says:
BUGS
Bootlogd works by redirecting the console output from the console
device. (Consequently bootlogd requires PTY support in the kernel con‐
figuration.) It copies that output to the real console device and to a
log file. There is no standard way of ascertaining the real console
device if you have a new-style /dev/console device (major 5, minor 1)
so bootlogd parses the kernel command line looking for console=...
lines and deduces the real console device from that. If that syntax is
ever changed by the kernel, or a console type is used that bootlogd
does not know about then bootlogd will not work.
Offline
Hi Terminator,
thanks for mentioning the bug from the manpage, indeed I forgot to have a look at this obvious place. Well, my /dev/console is major 5, minor 1, but my kernel command line does not contain any console= option at all. So I tried booting with additional parameter 'console=/dev/console' but that didn't help either. Well, meanwhile I found another thread mentioning the same problem. It would be interesting to know, if it works for most people or if simply hardly anybody uses /var/log/boot. I found it very helpful to google for specific error messages. Anyway, if somebody has an idea, how to further investigate this bug, I would be glad to hear it.
Cheers, Zmann
Offline
bootlogd is owned by sysvinit and is called from /etc/rc.sysinit:
grep bootlogd /etc/rc.sysinitDo you use iniscripts or systemd?
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline
Hi Leonid,
thanks for your answer, I'm using sysvinit. As I said in an earlier post: I see the line where bootlogd is started in /etc/rc.sysinit. Nevertheless it is obviously not started. If I start it by hand from commandline, I can see some shutdown messages in /var/log/boot after next boot process, but nothing from startup. Maybe it would be a good idea to add an strace to the call of bootlogd in /etc/rc.sysinit and send the output to a file?
Cheers, Zmann
Offline
Sorry for missing that... Before using strace, try adding "-l /root/boot.log" (see man bootlogd) and optionally a redirect for error messages to bootlogd call in rc.sysinit. This would tell you if bootlogd is indeed started.
Last edited by Leonid.I (2012-06-02 22:06:59)
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline
Meanwhile I found out, what went wrong with bootlogd: I have a separate partition for /var and at boot time it is obviously not mounted, but it is mounted later on and all the stuff in the now unvisible var directory on my root partition is hidden then. I will post a separate thread for that. Thanks to all who helped.
Cheers, Zmann
Offline
Just to clarify this issue: if bootlogd will find directory /var/log at boottime and if he succeeds in creating a file there, then he will write to this directory. If you did put /var on an own partition, this partition will be mounted later on in the bootprocess and hide the former content of /var/log. If you remove the artefact /var/log from your boot partition (it makes no sense to have data in the /var/log directory, if you mount a partition over it later on), bootlogd will write the log data to the correct partition.
Thanks to Leonid.I for pointing me to the right direction.
Cheers, Zmann
Offline