cs_show_cluster_transition(8)

📦 version 3.1.3, in opensuse-leap 16.0

💅 cs_show_cluster_transition — the ClusterTools2 manual, but make it make sense

okay bestie, so this page is cs_show_cluster_transition(8) — that's the man page name, and it lives in the ClusterTools2 family, and I'm about to explain the whole thing to you like we're texting at 1am. let's go 🫶

✨ NAME ✨

cs_show_cluster_transition — it goes digging through log files looking for cluster transition patterns. that's the whole gig. no cap.

✨ SYNOPSIS ✨

cs_show_cluster_transition [OPTION]

literally just the command, and optionally an option. that's it. slay.

✨ DESCRIPTION ✨

okay so cs_show_cluster_transition searches your log files for crmd cluster transition patterns. but bestie, hear me on this one — crmd only writes to the log on the DC node. so like… one node. the designated coordinator one. don't go looking on the other nodes and act surprised, i warned you 💀

every single cluster state transition is triggered by an event. any change of the cluster state? that's an event. the cluster also generates events on a regular base — f.e. every 900 seconds. and the normal state of the cluster is IDLE. like the cluster's default setting is just chilling. iconic honestly 🌸

currently known states are:

S_IDLE
S_POLICY_ENGINE
S_TRANSITION_ENGINE
S_STARTING
S_PENDING
S_ELECTION
S_INTEGRATION
S_FINALIZE_JOIN
S_NOT_DC

(yes, the original really does spell it "Currrently" — i'm keeping the energy but just so you know these are the states 💖)

✨ OPTIONS ✨

  • --help — shows help. the classic "what does this do again" button 🎀
  • --version — shows version. for when you gotta know what you're running.
  • --error — shows crmd errors. the messy parts. the drama. 🔥

✨ EXIT STATUS ✨

  • 0 — successful program execution. we ate. 👑
  • >0 — usage, syntax or execution errors. something went sideways, not the vibe 😭

✨ EXAMPLES ✨

just run it, bestie:

# cs_show_cluster_transition

or if you wanna be picky about what you see — filter for DC and for o.*line:

# cs_show_cluster_transition | grep -e "DC" -e "o.*line"

✨ FILES ✨

  • /usr/sbin/cs_show_cluster_transition — the program itself. the main character 💅
  • /etc/ClusterTools2/cs_show_cluster_transition — the configuration.
  • /etc/corosync/corosync.conf — the corosync configuration, which maybe defines the log file. maybe. it's giving mystery 🦋
  • /etc/products.d/ — the directory with product identification files.
  • /var/log/messages — the default log file. the one it actually looks at by default, iykyk.

✨ BUGS ✨

okay this is the part where we keep it real 🙈

currently SLES11 SP1 and SP2 are handled correctly. for SLES11 SP3 and SP4 only a sub-set of patterns is shown, because fields differ. and — big one — only /var/log/messages is parsed correctly. the optional corosync log has a different format, so like… yeah. 💀

feedback is welcome, please use the project page at: https://build.opensuse.org/package/show?package=ClusterTools2&project=home%3Afmherschel

✨ SEE ALSO ✨

go read these too, they're all connected 🧚

cs_show_error_patterns(8), cs_show_cluster_patterns(8), ptest(8), crm_attribute(8), crm_simulate(8), grep(1), syslog(8), logrotate(8), ClusterTools2(7), and http://www.clusterlabs.org/man/

(c) 2011-2014 L.Pinne, Germany.

cs_show_cluster_transition comes with ABSOLUTELY NO WARRANTY. for details see the GNU General Public License at http://www.gnu.org/licenses/gpl.html ⭐

and that's the whole page, bestie 🌈 — this version was rendered from the 03 Aug 2014 edition of the cs_show_cluster_transition(8) man page, part of ClusterTools2. mwah, go read your logs 💜

📦 where this page comes from