cs_show_cluster_patterns(8)

📦 version 3.1.3, in opensuse-leap 16.0

💅 cs_show_cluster_patterns(8) — the ClusterTools2 one, section 8 bestie 🎀

okay so picture this: it's like 3am, your cluster is being A Whole Thing, and you need to know what actually happened in the logs. That's this script. It's a section 8 system admin tool from ClusterTools2, and it's literally just out here searching your log files for cluster patterns so you don't have to grep blindly like a lost little butterfly 🦋

✨ NAME ✨

cs_show_cluster_patterns — search log files for cluster patterns 🔍

✨ SYNOPSIS ✨

cs_show_cluster_patterns OPTION

✨ DESCRIPTION ✨

cs_show_cluster_patterns searches log files for cluster patterns. That's the whole vibe, that's the job 🫶

⚠️ important heads-up bestie: most cluster components do logging to their local node only. So no cap, don't be shocked when Node B's drama isn't showing up in Node A's logs — that's just how it is 💀

✨ OPTIONS ✨

  • --help — show help. your classic "what even is this" button 🙈
  • --version — show version. so you can prove which one you're on 👑
  • --writecfg — show some internal variables. behind-the-scenes peek 🎀
  • --show — show all patterns. everything, the full menu ✨
  • --fencing — show fencing patterns. the "somebody got kicked out" section 🔥
  • --migration — show migration patterns. resources moving around, main character energy 💅
  • --count — count total for each pattern. numbers girlies rise 🧮
  • --zip — count from compressed logs, too. This could take some time. ⏳ lowkey a patience test

🌸 EXAMPLES 🌸

show migrations — like, which resources went where?

# cs_show_cluster_patterns -m

count occurance of patterns, show non-null only:

# cs_show_cluster_patterns -c | grep -v "=.0$"

show whole lines, but only for January. Useful if logs contain December as well:

# cs_show_cluster_patterns -s | grep "^Jan"

iykyk — that December/January thing is foreshadowing, keep reading 🍓

✨ EXIT STATUS ✨

  • 0 — Successful program execution. slay, it worked ✨
  • >0 — Usage, syntax or execution errors. it's giving "you typed something cursed" 😭

🦋 FILES 🦋

  • /usr/sbin/cs_show_cluster_patterns — the program itself. the moment 💖
  • /etc/ClusterTools2/cs_show_cluster_patterns — the configuration. its little settings corner 🎀
  • /etc/corosync/corosync.conf — the corosync configuration, maybe defining log file. "maybe" doing a lot of work there, ngl 👀
  • /var/log/messages — the default log file. old reliable ⭐

💀 BUGS 💀

okay listen, real talk:

This script depends on LC_MESSAGES respective RC_LANG set to en_US or C. So if your locale is doing its own thing, this script is gonna be confused, and that's on the locale fr fr 🙈

Furthermore the scripts sort output by month. This results in wrong order of lines, if a logfile f.e. contains December and January. Like, December before January? in this economy? yeah, the sort doesn't know about calendar years 🗓️💀 (this is the December thing from the examples, told you)

Feedback is welcome, please mail to feedback@suse.com 📬 they genuinely want to hear from you!

🧚 SEE ALSO 🧚

cs_show_error_patterns(8), cs_show_cluster_transition(8), grep(1), syslog(8), logrotate(8), corosync.conf(5), ClusterTools2(7) — the whole friend group, go say hi 🫶

(c) 2011-2019 L.Pinne, Germany. cs_show_cluster_patterns 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 iconic little manual is dated 01 Nov 2019, it ships with ClusterTools2, and it was written and maintained by L.Pinne, Germany — go off, legend 👑💜

📦 where this page comes from