On Thu, 31 May 2018 at 12:58 -0000, Jarrod Johnson wrote:
> > Oh yeah, another complaint for the DMTF folks: the system clock
> > should be in UTC, not "local time".
>
> Heh, confusion over whether timestamps are local or remote caused me
> to incorporate time zone correction to reventlog (and nodeventlog).
> Every time it pulls log it asks 'what time do you think it is *right
> now*' and adjusts all the timestamps it sees according to how
> different the current claimed time is from what the time is. It's
> why reventlog/nodeventlog disagree with ipmitool on timestamps.
> Well, that confusion and the propensity for BMCs to have whatever
> unset clock people feel like.
I almost mentioned that. I periodically use reventlog to save the
eventlog to a file. The xCAT timestamp correction works okay, except
sometimes the computed adjustment varies by a second or so. This
makes doing diffs between reventlog output not work like I would like
(i.e. being able to see just any new entries).
This is one place I use impitool. I have about 8 years of eventlog
information for all of our nodes, but I've never taken the time to
understand some of the needed sensor status/state or whatever
conversions needed to make the information meaningful. I actually
just depend upon the xCAT reventlog interpreted information (another
plus for xCAT).
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
