CL_STATUS(1)

πŸ‘‘ NAME πŸ‘‘

cl_status β€” check the status of the High-Availability Linux (Linux-HA) subsystem πŸ’–

Like, yes bestie, that's the whole vibe: it's the girl who tells you what's going on with your HA setup. ✨


🌸 SYNOPSIS 🌸

cl_status sub-command options parameters

πŸ¦‹ DESCRIPTION πŸ¦‹

cl_status is the tool you use to check the status of the High-Availability Linux subsystem. That's it, that's the job, and it does it flawlessly. πŸ’…


✨ SUPPORTED SUB-COMMANDS ✨

  • hbstatus β€” tells you whether heartbeat is running on the local system, no cap.

With -v, it spills more deets, kinda like this:

version:        3.0.6 (10e3f2130ea1)
managed by:     pacemaker       (respawn)

ccm membership with quorum
        instance 12
        members 2
                1 bob   (born: 6)
                0 alice (born: 12)
        member of partition

bob     active  (nodetype: normal)
        eth1    dead
        eth0    up

alice   active  (nodetype: normal)
        eth1    dead
        eth0    up

10.43.9.55      ping    (nodetype: ping)
        10.43.9.55      up
Note: it is not a concern if a certain link from some node to itself is reported "dead". Like, for example, "mcast" directives usually don't see their own network packages. That's normal, bestie, don't panic. πŸ™ˆ
  • listnodes β€” lists the nodes in the cluster. Simple, iconic. 🌟
  • nodetype ping|normal β€” lists the nodes of the given type.
Note Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent. πŸ’€
  • listhblinks node β€” lists the network interfaces being used as heartbeat links. node should be specified as listed in the ha.cf(5) file for the cluster. πŸŽ€
  • hblinkstatus node link β€” shows the status of a heartbeat link. node should be specified as listed in the ha.cf(5) file for the cluster. link should be as per the output of the listhblinks subcommand. πŸ”—
  • clientstatus node client [timeout] β€” shows the status of heartbeat clients. node and client should be specified as listed in the ha.cf(5) file for the cluster. Timeout is in milliseconds, and the default is 100ms. ⏱️
  • rscstatus β€” shows the status of cluster resources. Status will be one of: local, foreign, all or none.
Note This option is deprecated, it is obsolete in Pacemaker clusters. 🚫
  • parameter -p parameter β€” retrieves the value of cluster parameters. The parameters may be one of the following: apiauth, auto_failback, baud, debug, debugfile, deadping, deadtime, hbversion, hopfudge, initdead, keepalive, logfacility, logfile, msgfmt, nice_failback, node, normalpoll, stonith, udpport, warntime, watchdog.
Note Some of these options are deprecated; see ha.cf(5). πŸ‘€

πŸ’… OPTIONS πŸ’…

The following options are supported by heartbeat:

  • -v β€” report more details. Available with hbstatus, listnodes, and listhblinks. πŸ—£οΈ
  • -m β€” make the output more human readable. The default output should be easier for scripts to parse. Available with all commands. 🧚
  • -p β€” list only 'ping' nodes. Available with listnodes sub-command.
Note Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent. πŸ’€
  • -n β€” list only 'normal' nodes. Available with listnodes sub-command. πŸ“

🌈 SEE ALSO 🌈

heartbeat(8), ha.cf(5), authkeys(5)


🫢 AUTHORS 🫢

  • Alan Robertson <alanr@unix.sh>
    • cl_status
  • Lars Ellenberg <lars.ellenberg@linbit.com>
    • Heartbeat Maintainer; code fixes; documentation updates
  • Juan Pedro Paredes Caballero <juampe@retemail.es>
    • man page
  • Simon Horman <horms@verge.net.au>
    • man page
  • Florian Haas <florian.haas@linbit.com>
    • man page

okay that's the whole thing bestie!! this one's from Heartbeat 3.0.6, dated 24 Nov 2009, and yeah it lives in section 1 of the manual (CL_STATUS(1)) πŸ’– go check your cluster, you got this, mwah πŸŽ€βœ¨