openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thu Nguyen OS <thu@os.amperecomputing.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Lost the threshold redfish log when update phosphor-sel-logger.
Date: Mon, 5 Apr 2021 15:28:28 +0000	[thread overview]
Message-ID: <E89303EA-4B66-4BAB-9A8B-C68EA398DA63@amperemail.onmicrosoft.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 741 bytes --]

Hi All,

After updating the base code of our openBmc source for Mt Jade platform to new version, I saw all of threshold warning/error of hwmon are losted.
Below is the sensor value and the configured thresholds.
[cid:image001.png@01D72A6A.FF772FA0]
Check in the web, the sensor value is bigger than warning threshold, but there are no log SEL entry in Redfish log.

After spending some time on debugging, I found that the below commit is the cause:
https://github.com/openbmc/phosphor-sel-logger/commit/25b26e162bd109b51aa09b16f26f9aa3d9d940fa

Remove this commit in phosphor-sel-logger, I can see the warning log in Redfish.
Do I need any configuration in phosphor-sel-logger to make this commit work?

Thanks.
Thu Nguyen.


[-- Attachment #1.2: Type: text/html, Size: 3472 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 41932 bytes --]

             reply	other threads:[~2021-04-05 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 15:28 Thu Nguyen OS [this message]
2021-04-13  7:51 ` Lost the threshold redfish log when update phosphor-sel-logger Thu Nguyen OS
2021-04-13 17:44   ` Bills, Jason M

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E89303EA-4B66-4BAB-9A8B-C68EA398DA63@amperemail.onmicrosoft.com \
    --to=thu@os.amperecomputing.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).