Kbox Structure
This topic describes the structure and service flow of the kbox.
Structure
The following figure shows the integrated structure and service flow of the kbox.
1. Temporarily, the exception information storage does not support the BMC or net/ram dump mode.
2. The current version supports only the following exception scenarios: OOM, OOPS (die), panic, and deadlock.
Service Flow
- The kbox module modifies the configuration file. Based on the actual situations, the kbox module configures the product information, scenarios for capturing exception information, and dump devices based on the configuration file (/etc/kbox/config).
- The kbox starts in service mode. After reading the configuration file (/etc/kbox/config), the kbox sends the product information and exception scenarios to the kbox module as module parameters.
- Based on the storage device parameters specified in the configuration file (/etc/kbox/config), the kbox loads the drive of the corresponding storage device and registers the storage device with the kbox module.
- When an exception occurs and the exception information is captured by the kbox module, the kbox module records the exception information in the temporary storage region, and then synchronizes the exception information to the storage device.
- The user with the root rights can run the log export command to export the exception information to the /var/log/kbox/ directory from the storage device.
- By reading the exception information file, the user can obtain the exception information to identify the problems.