Once the userspace boot messages are gone from the console in Debian, they’re gone forever. How do I log all messages sent to the /dev/console device to a logfile under Debian Linux sever?
You need to use the bootlogd to record boot messages to a file called /var/log/boot. However, this is turned off by default. Edit /etc/default/bootlogd, enter:
# vi /etc/default/bootlogd
To run bootlogd at startup set it as follows:
BOOTLOGD_ENABLE=yes
After reboot you can see message in /var/log/boot:
# tail -f /var/log/boot
OR
# egrep -iw 'word1|err|warn' /var/log/boot
🐧 Get the latest tutorials on Linux, Open Source & DevOps via RSS feed or Weekly email newsletter.
🐧 5 comments so far... add one ↓
🐧 5 comments so far... add one ↓
Related Tutorials
| Category | List of Unix and Linux commands |
|---|---|
| Disk space analyzers | df • ncdu • pydf |
| File Management | cat • cp • mkdir • tree |
| Firewall | Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
| Network Utilities | NetHogs • dig • host • ip • nmap |
| OpenVPN | CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04 |
| Package Manager | apk • apt |
| Processes Management | bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time |
| Searching | grep • whereis • which |
| User Information | groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w |
| WireGuard VPN | Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04 |
Interesting…But I thought usually whatever is in console is usually piped to messages anyway
Setting BOOTLOGD_ENABLE=yes does not work in the current version of Ubuntu. This is a popular recommendation, but it ain’t gonna help :-(
https://bugs.launchpad.net/ubuntu/+source/boot/+bug/34165
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/306998
https://bugs.launchpad.net/upstart/+bug/328881
https://answers.launchpad.net/ubuntu/+question/2933
Thanks for the nice post ,
dj you are right regarding Ubuntu , i have tried the above method but it did not work for me (I am using ubuntu 9.10) but unfortunately i have just noticed your comment after applying the above method ……………………..
How do I do same with CentOS/RHEL?
Plz help Vivek!
Thanks for this post. Unfortunately I’m getting what seems to be some strange character muddling in the log, always at the end of each line, about the last one third. Is there any way to specify a charset for the log or some other solution?