Overview
This topic describes background and basic concepts of the kbox, to help you better understand the kbox.
Overview
The kernel of the Linux system is relative complex. Modules are closely associated with each other. Due to less efficient maintenance tools, the maintenance work is difficult to implement. Although the kernel is equipped with log recording systems such as the klogd and syslogd, logs may not be recorded (or cannot be recorded in a timely manner) in case of emergencies such as unexpected system reboot, kernel panic, and memory overflow. As a result, you cannot identify root causes of these problems.
To solve these problems and rescue lost kernel logs, the EulerOS provides the kbox feature. The kbox functions as the black box designed for the aircraft systems. Upon system exceptions, important information is recorded in a special channel (using the non-volatile storage). Therefore, you can analyze the system status upon the exceptions.
Feature Introduction
The kbox provides a mechanism that can record important information about the kernel upon system exceptions, and record the important information in the non-volatile storage devices. Based on the recorded information, you can analyze the causes of the system exceptions and locate the faults.
For example, when the kernel panic occurs, the kbox collects exception information generated by the kernel and saves the information in a temporary region. After collecting all information, the kbox dumps the information saved in the temporary region to the non-volatile storage devices (for example, the NVRAM) or the specified memory using the kdump function for further analysis.
The kbox only collects the kernel output information and function calling relationships that result in the system exceptions instead of sensitive data of the users. For details about how to disable the kbox, see Command References.
Components of the kbox
Table 9-1 describes the components of the kbox module.
Component |
Description |
|---|---|
Kbox |
Manage the non-volatile storage devices, and capture and save information generated for exceptions. |
Drive of the non-volatile storage device |
Provide read and write interfaces for the kbox. When the kbox is enabled, the corresponding drive module is loaded to register the storage device with the kbox. |
Non-volatile storage device |
Save information generated for exceptions. When exceptions occur, the kbox dumps the exception information to the non-volatile storage device. If no non-volatile storage device is configured, the kbox saves the logs using the kdump function. |
