[ClusterLabs] Discovering corosync-blackbox

Jan Friesse jfriesse at redhat.com
Wed May 13 08:11:00 EDT 2015


Ulrich Windl napsal(a):
> Hi!
>
> I just discovered corosync-blackbox, a too to find out what's going on, obviously ;-)
> Unfortunately the time stamps with seconds resolution seem to bit a bit like a joke, and supplying the data seems very redundant to me. Consider this example:

blackbox is really more for developers than average administrators (this 
doesn't mean they cannot use it/profit from using it). That's why it's 
so redundant.

> # corosync-blackbox | grep ringid
> ...
> rec=[867124327] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc116
> rec=[867124335] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc118
> rec=[867124385] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc122
> rec=[867124426] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc12a
> rec=[867124476] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc134
> rec=[867124484] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc136
> rec=[867124550] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc143
> rec=[867124616] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc150
> rec=[867124625] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc152
> rec=[867124671] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc15b
> rec=[867124718] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc164
> rec=[867124727] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc166
> rec=[867124792] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc173
> rec=[867124852] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc17f
> rec=[867124860] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc181
> rec=[867124920] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc18d
> rec=[867124968] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc197
> rec=[867124977] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc199
> rec=[867125039] time=[2015-05-13 08:47:19] Tracing(1) Messsage=Received ringid(172.20.16.1:2512) seq a0dc1a5
> ...
>
> More questions:
> "2512" is not the port configured; what is it? And should the "seq" be somewhat "gapless"? Or is the whole blackbox lossy?

2512 is monotonically increasing number (not port at all) and it 
increase on every membership change. Basically ringid is 
leader_ip:increasing_number.

Blackbox is and together isn't lossy. It's ring buffer so number of 
messages is limited and oldest messages are overwritten, but messages 
should be in order.


>
> What's the meaning of "Log Message=Can't store blackbox file: Success (0)"?

Corosync 1.4.x or 2.3.x?

Regards,
   Honza
>
>
> Regards,
> Ulrich
>
>
>
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>





More information about the Users mailing list