archive mirror
 help / color / mirror / Atom feed
From: "Bills, Jason M" <>
Subject: Re: Lost the threshold redfish log when update phosphor-sel-logger.
Date: Tue, 13 Apr 2021 10:44:23 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 4/13/2021 12:51 AM, Thu Nguyen OS wrote:
> Dear Zhikui Ren, Patrick Williams and Jason M. Bills,
> Do you have any comment in this?
> Dear Zhikui Ren,
> Do you verify this commit with the sensors which added thru phosphor-hwmon?
This issue was recently discussed here:

Since that discussion, this change to phosphor-dbus-interfaces was 
merged to add support for new threshold signals that contain the sensor 

I believe that corresponding changes can now be added to dbus-sensors, 
hwmon, and sel-logger to correctly handle these new signals to resolve 
the issue you see here.
> Regards.
> Thu Nguyen.
> *From: *Thu Nguyen OS <>
> *Date: *Monday, 5 April 2021 at 22:28
> *To: *"" <>
> *Subject: *Lost the threshold redfish log when update phosphor-sel-logger.
> 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.
> 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:
> 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.

      reply	other threads:[~2021-04-13 17:44 UTC|newest]

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

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:

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

  git send-email \ \ \ \

* 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).