Are you new to blogging, and do you want step-by-step guidance on how to publish and grow your blog? Learn more about our new Blogging for Beginners course and get 50% off through December 10th.
WordPress.com is excited to announce our newest offering: a course just for beginning bloggers where you’ll learn everything you need to know about blogging from the most trusted experts in the industry. We have helped millions of blogs get up and running, we know what works, and we want you to to know everything we know. This course provides all the fundamental skills and inspiration you need to get your blog started, an interactive community forum, and content updated annually.
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: Starting Check console baud rate…
Feb 22 19:13:49 c0280579 ol-consolebaud: Serial console is set to the default of 9600 baud. This can
Feb 22 19:13:49 c0280579 ol-consolebaud: result in stalls or lockups in error conditions requiring a
Feb 22 19:13:49 c0280579 ol-consolebaud: large number of console system messages. Please increase the
Feb 22 19:13:49 c0280579 systemd: ol-consolebaud.service: main process exited, code=exited, status=1/FAILURE
Feb 22 19:13:49 c0280579 ol-consolebaud: rate to the highest your system will allow (for instance, 115200
Feb 22 19:13:49 c0280579 systemd: Failed to start Check console baud rate.
Feb 22 19:13:49 c0280579 ol-consolebaud: or 57600). See Oracle KM Note 2648582.1 for more information.
Feb 22 19:13:49 c0280579 systemd: Unit ol-consolebaud.service entered failed state.
Feb 22 19:13:49 c0280579 systemd: ol-consolebaud.service failed.
Fix in this case is simple:
1.- Modify the GRUB2 configuration file:
2.- If the following lines are not in the file, please add them: