From: "chunhui.jia" <chunhui.jia@linux.intel.com>
To: "Thu Ba Nguyen" <tbnguyen1985@gmail.com>,
"Ramesh I I1" <rameshi1@in.ibm.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Re: phosphor-logging: entry() failed parse message.
Date: Tue, 10 Nov 2020 12:27:53 +0800 [thread overview]
Message-ID: <5FAA16C5.3050103@linux.intel.com> (raw)
In-Reply-To: <CALioo37f6Katzcag-hgA=u_spHOdeQw5WbvSapAs=qMyiwOxYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3128 bytes --]
The data embedded in your entry() is meta-data. Use '-overbose' option in journalctl command to print.
journalctl -ef -overbose
>>
Tue 2020-11-10 12:28:43.472063 UTC [s=93d61b6180db407d8f32924833a6954d;i=10c4;b=0ba0603a97814c2bb3d22f4857b5f964;m=13e4a3855c;t=5b3bfd1cbc915;x=bac5bbc519880cdf]
_UID=0
_GID=0
_CAP_EFFECTIVE=3fffffffff
_BOOT_ID=0ba0603a97814c2bb3d22f4857b5f964
_MACHINE_ID=b1d2788fe17541c0ba0363cd0f0aa699
_HOSTNAME=intel-obmc
_SYSTEMD_SLICE=system.slice
_TRANSPORT=journal
PRIORITY=3
CODE_FILE=/usr/src/debug/intel-ipmi-oem/0.1+gitAUTOINC+04a38ed10d-r0/recipe-sysroot/usr/include/phosphor-logging/log.hpp
CODE_LINE=76
CODE_FUNC=helper_log
TRANSACTION_ID=4091710023
SYSLOG_IDENTIFIER=ipmid
_PID=245
_COMM=ipmid
_EXE=/usr/bin/ipmid
_CMDLINE=ipmid
_SYSTEMD_CGROUP=/system.slice/phosphor-ipmi-host.service
_SYSTEMD_UNIT=phosphor-ipmi-host.service
_SYSTEMD_INVOCATION_ID=62df2ae5590c48a2b79ffe6843c3681c
MESSAGE=Failed to GetAll
INTF=xyz.openbmc_project.Inventory.Decorator.Ipmi
WHAT=sd_bus_call: org.freedesktop.DBus.Error.UnknownInterface: Unknown interface 'xyz.openbmc_project.Inventory.Decorator.Ipmi'.
PATH=/xyz/openbmc_project/inventory/system/powersupply/SOLUM_CO_IS162F22_PSU1
_SOURCE_REALTIME_TIMESTAMP=1605011323472063
2020-11-10
chunhui.jia
发件人:Thu Ba Nguyen <tbnguyen1985@gmail.com>
发送时间:2020-11-10 06:35
主题:Re: phosphor-logging: entry() failed parse message.
收件人:"Ramesh I I1"<rameshi1@in.ibm.com>
抄送:"OpenBMC Maillist"<openbmc@lists.ozlabs.org>
Thanks Ramesh,
But your commands are applied for some messages.
And don't answer my questions.
"Do I need to add any option when building?" to make phosphor-logging print message in entry().
Regards.
Thu Nguyen.
On Mon, Nov 9, 2020 at 11:04 AM Ramesh I I1 <rameshi1@in.ibm.com> wrote:
Hi Thu Nguyen,
Below link may help you to get more detailed log which you are referring.
https://github.com/openbmc/openbmc/wiki/Debugging-OpenBMC#journalctl
For example:
journalctl -o json-pretty MESSAGE="watchdog: Timed out"
Regards,
Ramesh
----- Original message -----
From: Thu Ba Nguyen <tbnguyen1985@gmail.com>
Sent by: "openbmc" <openbmc-bounces+rameshi1=in.ibm.com@lists.ozlabs.org>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Cc:
Subject: [EXTERNAL] Re: phosphor-logging: entry() failed parse message.
Date: Sat, Nov 7, 2020 6:11 PM
The output in BMC console will be:
phosphor-watchdog[534]: watchdog: Timed out
Regards.
Thu Nguyen
On Sat, Nov 7, 2020 at 7:38 PM Thu Ba Nguyen <tbnguyen1985@gmail.com> wrote:
Hi,
In openBmc, We are using phosphor-logging.
When I log:
log<level::INFO>(
"watchdog: Timed out",
entry("ACTION=%s", convertForMessage(action).c_str()),
entry("TIMER_USE=%s", convertForMessage(expiredTimerUse()).c_str()),
entry("TARGET=%s", target->second.c_str()));
The message in entry() is losted.
Do I need to add any option when building?
Thanks.
Thu Nguyen.
[-- Attachment #2: Type: text/html, Size: 8468 bytes --]
next prev parent reply other threads:[~2020-11-10 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 12:38 phosphor-logging: entry() failed parse message Thu Ba Nguyen
2020-11-07 12:39 ` Thu Ba Nguyen
[not found] ` <OF8D57E4C0.929A4052-ON0025861B.00159DF0-0025861B.00165862@notes.na.collabserv.com>
2020-11-09 22:35 ` Thu Ba Nguyen
2020-11-10 4:27 ` chunhui.jia [this message]
2020-11-10 5:00 ` Thu Ba Nguyen
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=5FAA16C5.3050103@linux.intel.com \
--to=chunhui.jia@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=rameshi1@in.ibm.com \
--cc=tbnguyen1985@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.