The serial console is helpful in troubleshooting difficult problems. This is useful if you are remotely administrate the Linux server even if the network has failed or crashed. In order to use serial console you need to configure GRUB boot loader and make changes to /etc/inittab file. Following instructions are tested on :
| Tutorial details | |
|---|---|
| Difficulty | Intermediate (rss) |
| Root privileges | Yes |
| Requirements | None |
| Time | N/A |
Step # 1: Serial redirection in the GRUB
Open the grub configuration file /boot/grub/menu.lst (Debian / Ubuntu Linux) or /boot/grub/grub.conf (Redhat/CentOS/Fedora Core Linux), enter:
# vi /boot/grub/grub.conf
Append the following lines below “hiddenmenu” option:
serial --unit=1 --speed=19200 terminal --timeout=8 console serial
- The first line tells GRUB to use the first serial port at a baud rate of 19200
- The second line gives the user 9 seconds to decide where GRUB should output it’s information.
- Please adjust port number and speed as per your setup.
Next make sure splashimage options is disabled as graphics can’t be displayed across the serial port. Remove splashimage line or just comment it out by prefixing # symbol:
#splashimage=(hd0,0)/grub/splash.xpm.gz
Step # 2: Enabling serial output from the Linux kernel
Find the kernel line (grub config file) which corresponds to your currently running kernel. Add the following at the end of that line – console=tty0 console=ttyS0,9600n8:
title Red Hat Enterprise Linux ES (2.6.9-42.0.10.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.0.10.ELsmp ro root=LABEL=/ console=tty0 console=ttyS1,19200n8
initrd /initrd-2.6.9-42.0.10.ELsmp.img
Save and close the file. When multiple console= options are listed, the Linux kernel will output (tty0, ttyS1) to both when possible. Now the kernel errors get logged with on both the normal VGA console and on the serial console.
Step #3: Logging in via the serial console
Finally open the /etc/inittab file, enter:
# vi /etc/inittab
Append the following line:
1:23:respawn:/sbin/agetty -h -L ttyS1 19200 vt100
Save and close the file. The above line allows you to login via the serial device. You are attaching agetty process to serial consol. Your Linux distribution may have the above line.
Step # 4: Test your setup
Next, reboot the server. Make sure you connect to the serial console using IPMI Java client or IPMIView Linux client. Finally, you should see the following message on screen:
Press any key to continue.
Now hit any key to launch GRUB on the serial console. Please note that if you do nothing, it will open server’s VGA console.
🐧 8 comments so far... add one ↓
| Category | List of Unix and Linux commands |
|---|---|
| File Management | cat |
| Firewall | Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04 |
| Network Utilities | 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 |
I started banging my head on the wall when I got to “now reboot your server”. Contradiction in terms.
The first column ‘1’ may cause problems on most RHEL5 installations. In my case, this cause the error ‘INIT: /etc/inittab[69]: duplicate ID field “1”‘ upon boot.
This is because the first column is a unique identifier, and is commonly used to identify tty1:
A better name would be something like S0:
it’s important to distinguish between centos5/rhel5 and c6/c7/r6/r7 as serial console is much easier in the latter as it doesn’t need you to do anything other than touch the kernel command line opts in grub config
This is awesome! Thank you very much this is what I was looking for. I got IPMI working on my Supermicro server!
Why people use console=tty0 in grub, afaik that tty/file doesn’t exist by default in any linux distribution, I realized that when people set tty0 in grub the system boots but without a valid tty and without login, you have to type alt+f1 to get a valid tty.
To fix it you have to set grub to a valid tty/console, like this:
GRUB_CMDLINE_LINUX=”console=tty1 console=ttyS0,115200n8″
Best regards.
why console just start on runleves 2,3? what about single user mode, for server recovery?
FYI, if you’re looking for same info on distros with SystemD, then look at here [fedoraproject.org]
im using this guide on both CentOS 6 and Ubuntu 14.10, i was able to configure correctly on CentOS however theres a problem in Ubuntu, i notice that the console only display during boot, after the VM is fully up, the console freezes. Here is the config i used:
/etc/default/grub
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=””
GRUB_CMDLINE_LINUX=”console=tty0 console=ttyS0,9600n8″
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD …)
#GRUB_BADRAM=”0x01234567,0xfefefefe,0x89abcdef,0xefefefef”
# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=serial
GRUB_SERIAL_COMMAND=”serial –unit=1 –speed=19200 terminal –timeout=8 console serial”
And then i create
/etc/init/ttyS1.conf
start on stopped rc RUNLEVEL=[12345]
stop on runlevel [!12345]
respawn
exec /sbin/getty -L 115200 ttyS1 vt102
Any idea?
Thanks,