I run Linux (Red Hat-based, CentOS, SL, versions 5 & 6) on a variety of Supermicro and other whitebox servers. Some have IPMI, some do not.
Some of these systems are attached to a Keyboard/monitor (KVM) console switch. Other systems are attached to a remote serial console. And newer servers are hooked into IPMI, and are available via either KVM-over-LAN Console Redirection or Serial over LAN (SOL).
With all of these methods we'd like to see consistent output on all of the serial console and on the KVM screens. For example, we want the ability to interact with the system from startup to shutdown, and we want to see the entire boot sequence. This includes seeing any messages printed by, and interacting with:
- The BIOS (This is handled by the BIOS console redirection in many modern BIOSes, and is independent from the Operating System)
- The bootloader (Grub 0.97, in this case)
- See messages printed by the kernel
- See messages printed by
fsck, such as during lengthy
fscks of large filesystems. On a system with a serial console, sometimes
fsckis sitting there doing nothing, waiting for a Sysadmin to type in a password. But the sysadmin may not see this password prompt unless we happen to remember to log into the serial console.
- See messages printed by programs during the startup session
Starting sshd: [ FAILED ] typo in sshd_config on line 171)
login:prompt , and allow me to log into the system.
I've tried a few methods, but it seems that no matter what I put in
grub.conf, some messages are printed to either the monitor or the serial console, but not both.
Is it possible to tell the bootloader, Linux kernel, OS, etc. to print all messages to the attached monitor and too the serial console?