Whatsup(1)

πŸ“¦ version 1.14, in epel 9, fedora 43, fedora 44

πŸ’– WHATSUP πŸ’–

okay bestie, gather round, because this is whatsup(1) from the Whatsup manual, and it is literally your cluster's group chat read receipts.


✨ NAME ✨

whatsup β€” list up and/or down nodes in a cluster πŸ¦‹


🌸 SYNOPSIS 🌸

whatsup [OPTION]... [NODES]...

πŸ’… DESCRIPTION πŸ’…

so whatsup tells you which nodes in your cluster are currently up or down. periodt. it figures out the up/down tea based on info handed over by the nodeupdown(3) library, so you might need to set up backend components or clusterlists for nodeupdown(3) first. go peek at libnodeupdown(3) for that, bestie. 🫢

by default whatsup checks the status of every single node in the cluster β€” unless you name specific nodes on the command line. and here's a fun one: if the first node listed is "-", then nodes get read in from standard input. nodes can be in hostrange format, comma separated lists, or space separated lists. (HOST RANGES section below has the deets, keep scrolling πŸ’–) also, the hostnames you list must be the shortened names of hostnames. no long-form, no government names. πŸ™ˆ

now, the exit value of whatsup depends on which options you ran. if you used the default --updown option, the exit value is 0 if the command succeeds without error. if you used --up, and no nodes are specified via the command line or standard input, the exit value is 0 if all cluster nodes are up. if nodes are specified via the command line or standard input, the exit value wil be 0 if all the specified nodes are up. the behavior is similar for the --down option. iconic, honestly. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” print help and exit πŸ’œ
  • -v, --version β€” print version and exit ⭐
  • -o STRING, --hostname=STRING β€” server hostname (default=localhost)
  • -p INT, --port=INT β€” server port (default=8649)
  • -b, --updown β€” list both up and down nodes (default) ✨
  • -u, --up β€” list only up nodes 🌈
  • -d, --down β€” list only down nodes πŸ’€
  • -t, --count β€” list only node counts πŸ”’
  • -q, --hostrange β€” list nodes in hostrange format (default)
  • -c, --comma β€” list nodes in comma separated list
  • -n, --newline β€” list nodes in newline separated list
  • -s, --space β€” list nodes in space separated list
  • -m, --module β€” use a specific backend module for up-down calculations. 🧚
  • -r, --last-up-time β€” output last known up time of nodes and their current up or down state. heads up: this option may not be available on some configurations. 😭
  • -l, --log β€” enter whatsup logging mode. whatsup will regularly poll the backend tool to calculate up-down state changes and output them to the appropriate output. πŸ“
  • -f, --log-file β€” specify the log file whatsup should output logging information to. if not specified, defaults to stdout.
  • -e, --log-poll β€” specify the length in seconds the log mode of whatsup should regularly poll. default is 30 seconds.
  • -M, --monitor β€” monitor up-down state changes through event monitoring. πŸ‘€

πŸ¦‹ HOST RANGES πŸ¦‹

as mentioned up top, whatsup accepts ranges of hostnames in the general form:

prefix[n-m,l-k,...]

where n < m and l < k, etc., as an alternative to explicit lists of hosts. do not confuse this with regular expression character classes (also denoted by []). for example, foo[19] does not represent foo1 or foo9 β€” it represents a degenerate range: foo19. so don't come for me. πŸ’…

this range syntax is meant only as a convenience on clusters with a prefixNN naming convention, and specification of ranges should not be considered necessary β€” the list foo1,foo9 could be specified as such, or by the range foo[1,9]. both are valid, both slay.

some examples of range usage follow:

list all nodes among foo01,foo02,...,foo05 that are up and down

whatsup foo[01-05]

list all nodes among foo7,foo9,foo10 that are up and down

whatsup foo[7,9-10]
🚨 reminder bestie: some shells will interpret brackets ('[' and ']') for pattern matching. depending on your shell, it may be necessary to enclose ranged lists within quotes. for example, in tcsh, the above two examples should be executed as:
whatsup "foo[01-05]"
whatsup "foo[7,9-10]"

🌟 EXAMPLES 🌟

list all nodes that are up and down.

whatsup

list all nodes that are down

whatsup -d

list all nodes among foo[0-20] that are down

whatsup -d foo[0-20]

list all nodes that are up and down by their alternate names

whatsup -a

list all nodes among foo[5-25] that are up by their alternate names

whatsup -u -a foo[5-25]

list all nodes that are up in comma separated lists.

whatsup -u -c

list all nodes that are up among the nodes foo2, foo4, and foo8

whatsup -u foo2,foo4,foo8

only output the number of nodes that are up and down

whatsup -t

only output the number of up nodes

whatsup -u -t

only output the number of up nodes among foo[5-25]

whatsup -u -t foo[5-25]

πŸ“ FILES πŸ“

  • /usr/bin/whatsup

πŸ‘‘ SEE ALSO πŸ‘‘


🌈 ORIGIN 🌈

developed by Albert Chu <chu11@llnl.gov> on LLNL's Linux clusters. this software is open source and distributed under the terms of the Gnu GPL. 🫢


and that's the whole page, bestie β€” shoutout to LLNL for writing this one back in August 2003, before most of us could even type. πŸ’– stay up (or down, whatsup -d has you covered) πŸ¦‹βœ¨

πŸ“¦ where this page comes from