This service will be installed when you provision a VM on OCI.
But in some VM shapes this service will not start.
Additional information provided by Oracle Support about it:
“The ol-consolebaud service is a sanity check for the system console. Many OCI instances still use 9600 baud serial consoles, and this provides a check for it. The reason for the check is that slow system consoles can cause problems with diagnostics when a kernel bug occurs.”
You can list the failed services running:
systemctl list-units --state=failed
The output on my VM.Standard2.1 is:
[root@server ~]# systemctl list-units --state=failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● ol-consolebaud.service loaded failed failed Check console baud rate
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
[root@server ~]# systemctl status ol-consolebaud.service
● ol-consolebaud.service - Check console baud rate
Loaded: loaded (/usr/lib/systemd/system/ol-consolebaud.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-02-22 19:13:49 EST; 20h ago
Main PID: 982 (code=exited, status=1/FAILURE)
Feb 22 19:13:49 c0280579 systemd[1]: Starting Check console baud rate…
Feb 22 19:13:49 c0280579 ol-consolebaud[982]: Serial console is set to the default of 9600 baud. This can
Feb 22 19:13:49 c0280579 ol-consolebaud[982]: result in stalls or lockups in error conditions requiring a
Feb 22 19:13:49 c0280579 ol-consolebaud[982]: large number of console system messages. Please increase the
Feb 22 19:13:49 c0280579 systemd[1]: ol-consolebaud.service: main process exited, code=exited, status=1/FAILURE
Feb 22 19:13:49 c0280579 ol-consolebaud[982]: rate to the highest your system will allow (for instance, 115200
Feb 22 19:13:49 c0280579 systemd[1]: Failed to start Check console baud rate.
Feb 22 19:13:49 c0280579 ol-consolebaud[982]: or 57600). See Oracle KM Note 2648582.1 for more information.
Feb 22 19:13:49 c0280579 systemd[1]: Unit ol-consolebaud.service entered failed state.
Feb 22 19:13:49 c0280579 systemd[1]: ol-consolebaud.service failed.
Fix in this case is simple:
1.- Modify the GRUB2 configuration file:
vim /etc/default/grub
2.- If the following lines are not in the file, please add them:
GRUB_SERIAL_COMMAND="serial --unit=0 --speed=115200"
GRUB_TERMINAL="serial console"
3.- Looking for console=ttyS0,9600 in “GRUB_CMDLINE_LINUX” line and change it for “console=ttyS0,115200”.
4.- Regenerate the GRUB2 configuration:
grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
It would be nice to have an error free image from OCI.
And I’m still trying to access MOS note 2648582.1 mentioned above 🙂