Viewing Kbox Information

Prerequisites

• The kbox is running properly in the EulerOS.
• The dump medium is working properly.

Procedure

• Check the running status of the kbox. Run the following commands:

  systemctl  status  kbox kbox.service - Crash message collector Loaded: loaded (/usr/lib/systemd/system/kbox.service; disabled) Active: active (exited) since Thu 2015-11-26 10:39:47 EST; 13s ago Process: 26545 ExecStart=/usr/sbin/kbox start (code=exited, status=0/SUCCESS) Main PID: 26545 (code=exited, status=0/SUCCESS) 
  
  Nov 26 10:39:46 localhost.localdomain kbox[26545]: kbox: kbox module has been loaded successfully! Nov 26 10:39:46 localhost.localdomain kbox[26545]: driver: drivers have been loaded successfully! Nov 26 10:39:47 localhost.localdomain systemd[1]: Started Crash message collector.

• View the output information.
  • If the active state is displayed, the kbox is running properly, as shown in the following figure.

  • If the failed state is displayed, the kbox is not loaded to the system, as shown in the following figure.

• View the temporary storage region of the system.

  After the kbox is started, by default, it creates multiple temporary storage regions to save the corresponding logs. Run the following command to view the existing storage regions in the system:

  the effective info in /etc/kbox/config:
  
  ------------- product      info -------------
  product       name: euler
  version     number: V200R002C10
  frame       number: 1
  slot        number: 0
  locate        info: 0
  
  ------------- enabled    events -------------
  panic_event    die_event      oom_event      
  rlock_event    oom_call_panic
  
  
  ------------- enabled  storages -------------
  hmem  
  
  
  the regions and storages list: 
  
  ------------- regions      list -------------
  console die message oom panic rlock 
  
  ------------- storages     list -------------
  hmem 

  Table 9-7 describes the temporary storage regions.

  Table 9-7 Description of storage regions

  Name	Description
  console	Saves log information output to the console after the storage exception occurs. If excessive information is output, the earliest information will be overwritten. The size of this storage region is 32 KB.
  die	Saves exception information captured when the kernel process encounters the OOPS (memory destroyed or using a null pointer) event. The size of this storage region is 128 KB.
  message	Saves the latest 64 KB information output by the kernel when the memory exception occurs.
  oom	Saves the information captured for the OOM event. The size of this storage region is 256 KB.
  panic	Stores the exception information captured when a panic event occurs. The size of the temporary storage area is 32 KB.
  rlock	The temporary storage area is used to store the exception information captured during rlock. The size of the temporary storage area is 256 KB.

• View the global information of the storage device.

  View the storage devices registered in the system.

  The storage devices indicate the storage mediums registered in the kbox module, including the NVRAM, PCIE device memory, and BMC device memory. After an exception occurs, the kbox updates the log information saved in the temporary storage regions to these storage devices. Currently, the CloudEdge uses the HMEM (ordinary memory) as the storage device by default. An example is as follows: