phosphor-logging: entry() failed parse message.

[Thu Ba Nguyen]

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 at 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 at gmail.com>
> Sent by: "openbmc" <openbmc-bounces+rameshi1=in.ibm.com at lists.ozlabs.org>
> To: OpenBMC Maillist <openbmc at 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 at 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.
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20201110/53a63f37/attachment.htm>