openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: SEL Event logs in Redfish
Date: Tue, 1 Jun 2021 12:05:12 -0700	[thread overview]
Message-ID: <85157600-4832-42bd-8f4d-87757153b732@linux.intel.com> (raw)
In-Reply-To: <SG2PR04MB30931F4EAC5DC1D4E968631EE1229@SG2PR04MB3093.apcprd04.prod.outlook.com>



On 5/28/2021 1:58 AM, Jayashree D wrote:
> Classification: Public
> 
> Hi Jason,
> 
> In journalctl log, I found that the sensor value is crossed the threshold value.
> But when I tried in Redfish API, I am not able to see any logs, whether anything I am missing here ?
> Could you please provide suggestions on this .
Unfortunately, we ran into trouble trying to persist the journal to 
flash, so we have one additional layer where rsyslog watches for any 
journal entries that have a "REDFISH_MESSAGE_ID" metadata and logs them 
to '/var/log/redfish' where bmcweb pulls them for the Redfish EventLog.

https://github.com/openbmc/openbmc/blob/master/meta-intel-openbmc/meta-common/recipes-extended/rsyslog/rsyslog/rsyslog.conf#L66

If you have the journal event, I'd check if you have 'var/log/redfish' 
populated with that event.  If not, you may need to add the above config 
to rsyslog to create it and that will hopefully fix the event in Redfish.

Thanks,
-Jason
> 
> root@tiogapass:~# journalctl | grep adc
> Jan 01 00:13:46 tiogapass adcsensor[298]: Sensor _MB_P5V low threshold 4.52 assert: value 4.51 raw data 1337
> 
> curl -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Systems/system/LogServices/EventLog/Entries
> {
>    "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/Entries",
>    "@odata.type": "#LogEntryCollection.LogEntryCollection",
>    "Description": "Collection of System Event Log Entries",
>    "Members": [],
>    "Members@odata.count": 0,
>    "Name": "System Event Log Entries"
> }
> 
> Thanks,
> Jayashree
> 
> On 5/24/2021 8:15 AM, Bruce Mitchell wrote:
>> On 5/24/2021 06:41, Jayashree D wrote:
>>>
>>> Hi Team,
>>>
>>> I need some clarification on SEL Logs.
>>> In SEL Event logs, when the error is injected manually , I can able
>>> to see the error logs in "ipmitool sel list" command.
>>> Whether it will also reflect in Redfish API ?
> I am mostly familiar with the journal-bases SEL logging.  In that case, phosphor-sel-logger will detect the error and log it to both IPMI SEL and Redfish at the same time:
> https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fopenbmc%2Fphosphor-sel-logger%2Fblob%2Fmaster%2Finclude%2Fthreshold_event_monitor.hpp%23L272&amp;data=04%7C01%7Cjayashree-d%40hcl.com%7C1e6f287fb3d24d154be508d91f11ef7d%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637574984193449537%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8JHAtQ7FBZSDtVoM3b0MGi2OhBQDNB16j0Pko0jg7p8%3D&amp;reserved=0.
> 
> It may also depend on how you are manually injecting the error.
> 
>>>
>>> Could you please help me in this.
>>>
>>> Thanks,
>>> Jayashree
>>>
>>> ::DISCLAIMER::
>>> ________________________________
>>> The contents of this e-mail and any attachment(s) are confidential
>>> and intended for the named recipient(s) only. E-mail transmission is
>>> not guaranteed to be secure or error-free as information could be
>>> intercepted, corrupted, lost, destroyed, arrive late or incomplete,
>>> or may contain viruses in transmission. The e mail and its contents
>>> (with or without referred errors) shall therefore not attach any
>>> liability on the originator or HCL or its affiliates. Views or
>>> opinions, if any, presented in this email are solely those of the
>>> author and may not necessarily reflect the views or opinions of HCL or its affiliates.
>>> Any form of reproduction, dissemination, copying, disclosure,
>>> modification, distribution and / or publication of this message
>>> without the prior written consent of authorized representative of HCL
>>> is strictly prohibited. If you have received this email in error
>>> please delete it and notify the sender immediately. Before opening
>>> any email and/or attachments, please check them for viruses and other
>>> defects.
>>> ________________________________
>>>
>>
>> Hi Jayashree,
>>
>> I suggest you connect with Jason Bills on SEL.
>>
>>
> 
> 

  reply	other threads:[~2021-06-01 19:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28  8:58 SEL Event logs in Redfish Jayashree D
2021-06-01 19:05 ` Bills, Jason M [this message]
2021-06-02  2:32   ` Lei Yu
2021-06-02 16:59     ` Bills, Jason M
2021-06-03  9:38       ` Lei Yu
  -- strict thread matches above, loose matches on Subject: below --
2021-05-24 13:41 Jayashree D
2021-05-24 15:15 ` Bruce Mitchell
2021-05-24 17:11   ` 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=85157600-4832-42bd-8f4d-87757153b732@linux.intel.com \
    --to=jason.m.bills@linux.intel.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).