From: Lei Yu <yulei.sh@bytedance.com>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>
Cc: openbmc <openbmc@lists.ozlabs.org>
Subject: Re: SEL Event logs in Redfish
Date: Wed, 2 Jun 2021 10:32:55 +0800 [thread overview]
Message-ID: <CAGm54UFm59ApCAV7DKdgfUGfjdok8dVs8ng6Brj0VXxMsrj=AQ@mail.gmail.com> (raw)
In-Reply-To: <85157600-4832-42bd-8f4d-87757153b732@linux.intel.com>
On Wed, Jun 2, 2021 at 3:05 AM Bills, Jason M
<jason.m.bills@linux.intel.com> wrote:
>
>
>
> 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.
There is a limitation about the way to log SEL event to
/var/log/redfish, that it only appears in redfish event logs, but not
in ipmi sel.
On g220a it still uses the logging service to represent the event log
(see [1]), and ipmid is updated to consume the logging entries to get
the SEL entries.
The missing part is in bmcweb that it does not support the event log
entries from DBus. We could probably add some new code to make it
support consuming data from logging service, and it could be
implemented under a config, so that the user could config which data
source to get event log at compile time.
[1]: https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Logging/SEL.metadata.yaml
--
BRs,
Lei YU
next prev parent reply other threads:[~2021-06-02 2:34 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
2021-06-02 2:32 ` Lei Yu [this message]
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='CAGm54UFm59ApCAV7DKdgfUGfjdok8dVs8ng6Brj0VXxMsrj=AQ@mail.gmail.com' \
--to=yulei.sh@bytedance.com \
--cc=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).