hexadecimal epochs in log messages?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello all,

I've bumped into log messages on the monitors showing epochs as hexadecimal. And being inconsistent at that, mind you, as consecutive messages will end up having different representations of decimal numbers; e.g.,

2018-05-25 23:08:15.483 7f5df53dc700 20 mon.b@3(peon).osd e10 send_pg_creates not using stale creating_pgs@f 2018-05-25 23:08:15.483 7f5df53dc700 20 mon.b@3(peon).osd e10 send_pg_creates not using stale creating_pgs@f 2018-05-25 23:08:15.483 7f5df53dc700 20 mon.b@3(peon).osd e10 send_pg_creates not using stale creating_pgs@f 2018-05-25 23:08:15.487 7f5df5bdd700 20 mon.b@3(peon).osd e16 send_pg_creates osd.1 from 16 : epoch 16 4 pgs

Funny enough, in a teuthology cluster this only affect a couple of different monitors. As far as I can see, 7 out of 9 monitors are not showing symptoms of this.

Given not all the monitors are affected, and that I didn't see any specific change as of late in our PRs, I'm tempted to rule out a code change in Ceph as being the culprit. But... what could it be? Different stl versions due to different distros? Compilers? Cosmic rays?

Thoughts appreciated.

  -Joao

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux