COROSYNC-BLACKBOX(8)
π COROSYNC-BLACKBOX π
ok so bestie, this is corosync-blackbox β it lives in the System Manager's Manual section (that's section 8, the big-girl admin section, iykyk) and it's genuinely the most β¨ dramatic β¨ little script in the whole cluster. no cap.
β¨ NAME β¨
corosync-blackbox β dump the live "flight data" straight outta the corosync "blackbox", like a plane crash investigation but make it cluster. π«π
πΈ SYNOPSIS πΈ
corosync-blackbox
that's it. no flags, no args, no notes. she takes zero options and she serves anyway. main character energy fr fr. π
π¦ DESCRIPTION π¦
so here's the tea: corosync-blackbox pokes corosync and tells it to write its "flight data" out to a file. then it runs qb-blackbox, which prints all that data out for you to read. that's the whole vibe. π
like literally: trigger the dump, then replay the dump. two steps, one command, iconic behaviour.
π EXAMPLES π
wanna see the current "flight data"? say less, bestie:
$ corosync-blackbox
Starting replay: head [74205] tail [0]
rec=[1] Log Message=Corosync Cluster Engine ('1.2.1'): started
and ready to provide service.
[...]
rec=[2607] Log Message=Delivering MCAST message with seq a to
pending delivery queue
rec=[2608] Log Message=downlist received left_list: 2
rec=[2609] Log Message=chosen downlist from node r(0)
ip(192.168.100.11)
Finishing replay: records found [2609]
see how it starts with Starting replay: head [74205] tail [0], spits out every rec=[...] line, and then closes with Finishing replay: records found [2609]? that's the whole flight recorder arc, beginning to end. obsessed. π₯
π SEE ALSO π
go read these too, they're the friend group:
π AUTHOR π
Angus Salkeld wrote this one. legend behaviour. π«Ά
ok that's the whole page, bestie!! this beauty is from the System Manager's Manual, dated 2010-05-30, and it answers to the name COROSYNC-BLACKBOX(8). go dump some flight data, you got this πβ¨π¦πΈπ
π¦ where this page comes from
- debian bookworm: corosync 3.1.7-1+deb12u2 Β· BSD-3-Clause
- debian trixie: corosync 3.1.9-2+deb13u1 Β· BSD-3-Clause
- epel 9: corosync 3.1.10-0.2.el9.1 Β· BSD-3-Clause
- fedora 43: corosync 3.1.10-3.fc43 Β· BSD-3-Clause
- fedora 43: corosync 3.1.9-5.fc43 Β· BSD-3-Clause
- fedora 44: corosync 3.1.10-4.fc44 Β· BSD-3-Clause
- fedora 44: corosync 3.1.10-6.fc44 Β· BSD-3-Clause
- nixos 26.05: corosync 3.1.9
- nixpkgs unstable: corosync 3.1.9
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- ubuntu jammy: corosync 3.1.6-1ubuntu1 Β· BSD-3-Clause
- ubuntu jammy: corosync 3.1.6-1ubuntu1.2 Β· BSD-3-Clause
- ubuntu noble: corosync 3.1.7-1ubuntu3 Β· BSD-3-Clause
- ubuntu noble: corosync 3.1.7-1ubuntu3.2 Β· BSD-3-Clause
- ubuntu questing: corosync 3.1.9-2ubuntu1
- ubuntu questing: corosync 3.1.9-2ubuntu1.1
- ubuntu resolute: corosync 3.1.9-2ubuntu3 Β· BSD-3-Clause
- ubuntu stonking: corosync 3.1.10-3ubuntu1 Β· BSD-3-Clause
- Copyright (C) 2010 Red Hat, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms