commit | 7c2810b482786ab2d05cf81633d6abb6ec577212 | [log] [tgz] |
---|---|---|
author | JinFuLin <JeffLin2@quantatw.com> | Fri Dec 02 13:55:28 2022 +0800 |
committer | JeffLin2 <JeffLin2@quantatw.com> | Tue Dec 13 00:53:41 2022 +0000 |
tree | feb8e6ba4fe8e9fe879506711663b44255b67baa | |
parent | 120486dce9fd5665ee8b4ef54248184b2d02903e [diff] |
Add host error event monitor Add host error event monitor to record event found by host-error-monitor and then add IPMI SEL record to journal. Tested: Test with the following PRs: https://gerrit.openbmc.org/c/openbmc/host-error-monitor/+/59127 https://gerrit.openbmc.org/c/openbmc/host-error-monitor/+/59129 https://gerrit.openbmc.org/c/openbmc/host-error-monitor/+/59130 Trigger host error and check result in "ipmitool sel" is as expected. Signed-off-by: JinFuLin <JeffLin2@quantatw.com> Change-Id: I72a49d62d9c3c4248ed8d748aebe2c8171221078
The SEL Logger daemon handles all requests to add new IPMI SEL records to the journal. SEL records stored in the journal are identified by the standard MESSAGE_ID metadata. Other metadata fields are used to store event-specific information for each record.
SEL records are identified in the journal using the MESSAGE_ID field.
The MESSAGE_ID for SEL records is "b370836ccf2f4850ac5bee185b77893a".
The additional metadata fields for a SEL record are
IPMI_SEL_RECORD_ID = Two byte unique SEL Record ID IPMI_SEL_RECORD_TYPE = The type of SEL entry (system or OEM) which determines the definition of the remaining bytes IPMI_SEL_GENERATOR_ID = The IPMI Generator ID (usually the IPMB Slave Address) of the requester IPMI_SEL_SENSOR_PATH = D-Bus path of the sensor in the event IPMI_SEL_EVENT_DIR = Direction of the event (assert or deassert) IPMI_SEL_DATA = Raw binary data included in the SEL record
The SEL Logger daemon exposes an interface for manually adding System and OEM type SEL events, and provides the capability to monitor for types of events and log them automatically.
The interface for System type events requires
The interface for OEM type events requires
The MESSAGE_ID and IPMI_SEL_RECORD_ID metadata fields are added by the daemon.
The SEL Logger daemon can be configured to watch for specific types of events and automatically log SEL records for them.
As an example, the SEL Logger has a "threshold event monitor" which implements a D-Bus match for any "PropertiesChanged" event on the xyz.openbmc_project.Sensor.Threshold
interface. The handler then checks for any new threshold events and logs SEL records accordingly.