All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Spinler <mspinler@linux.vnet.ibm.com>
To: Patrick Venture <venture@google.com>
Cc: Yong Li <yong.b.li@linux.intel.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: journal log messages are missing with latest version
Date: Thu, 03 Jan 2019 12:12:38 -0600	[thread overview]
Message-ID: <e7a140e4aaeb2bed76a9d36cbc422ea6@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAO=notz4=R-v8yoyYRqRDBBvSaB6mBUNAaZbeQcf0a_wCHQ7qw@mail.gmail.com>

On 2019-01-02 13:09, Patrick Venture wrote:
> On Thu, Dec 20, 2018 at 4:38 PM Yong Li <yong.b.li@linux.intel.com> 
> wrote:
>> 
>> 
>> 
>> Hi Patrick,
>> 
>> 
>> 
>> I encountered a problem after upgrade to the latest opnebmc version:
>> 
>> 
>> 
>> These log messages in ipmid are missing with the “journalctl -f”.
> 
> Which log messages?


This showed up on all of our systems too, anything logged using 
phosphor-logging
is missing from the journal.  I even ended up using a git bisect to also 
narrow
it down to:

phosphor-logging: srcrev bump 30047bf964..31552c05e2

     Patrick Venture (5):
           add sdjournal interface to inject tests
           test: use only one main library
           bugfix: add fixes to mock class
           bugfix: rename method to match implementation
           test: add test to force building of sdjournal mock


> 
>> 
>> 
>> 
>> My tests shows that the blow change is related, after I revert it, I 
>> can get these log messages.
>> 
>> 
>> 
>> Did you meet such issue, or any suggestions/comments to narrow down 
>> this issue?
>> 
>> https://github.com/openbmc/phosphor-logging/commit/59a6b1f27e83066baa6f3711c88d6a3b9a5c4d49
>> 
>> add sdjournal interface to inject tests
> 
> There were some follow-on patches for phosphor-logging that you
> shouldn't need -- it's
> 
> What SHA is for your https://github.com/openbmc/phosphor-host-ipmid ?
> (so I know what version of that is in use by you).
> 
> Checking the HEAD version of
> https://github.com/openbmc/phosphor-host-ipmid/blob/master/Makefile.am,
> I see it's including the proper libs to get the full phosphor-logging
> objects.
> 
>> 
>> 
>> 
>> Thanks,
>> 
>> Yong

  reply	other threads:[~2019-01-03 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21  0:38 journal log messages are missing with latest version Yong Li
2019-01-02 19:09 ` Patrick Venture
2019-01-03 18:12   ` Matt Spinler [this message]
2019-01-03 19:19     ` Patrick Venture
2019-01-03 22:28       ` Patrick Venture
2019-01-03 22:33         ` Patrick Venture
2019-01-04  1:20           ` Li, Yong B
2019-01-04 14:58             ` Patrick Venture

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=e7a140e4aaeb2bed76a9d36cbc422ea6@linux.vnet.ibm.com \
    --to=mspinler@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.com \
    --cc=yong.b.li@linux.intel.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.