Hi Jeff,
You need to use “-o verbose” when you using journalctl command as below:
journalctl --system --no-pager -o verbose

Best regards,
Tim

From: openbmc [mailto:openbmc-bounces+chli30=nuvoton.com@lists.ozlabs.org] On Behalf Of Jeff Chan
Sent: Wednesday, November 27, 2019 10:40 AM
To: openbmc@lists.ozlabs.org
Subject: phosphor logging

Dear openbmc developer,

I'm debugging chassis power on issue, and found that I can't use journalctl to display debug information, for example:

in chassis_state_manager.cpp
Chassis::Transition Chassis::requestedPowerTransition(Transition value)
{

    log<level::INFO>("Change to Chassis Requested Power State",
                     entry("CHASSIS_REQUESTED_POWER_STATE=%s",
                           convertForMessage(value).c_str()));
    executeTransition(value);
    return server::Chassis::requestedPowerTransition(value);
}

but journalctl only display "Change to Chassis Requested Power State", the "CHASSIS_REQUESTED_POWER_STATE=%s" part is missed, can someone tell me how to get it back? I tried google but can't find the answer.

And that will be great if someone can guide me how to port and debug power control, I tried "obmutil chassison" in debug console but doesn't work. I can't find detailed document about porting.

Thank you!

Jeff




________________________________
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.