fence_kdump_send(8)
π fence_kdump_send β bestie edition π
okay so this is fence_kdump_send, from the System Manager's Manual, section 8. yes she's a real one. come sit, we're gonna get through this together π«Ά
β¨ NAME β¨
fence_kdump_send β send kdump acknowledgement message to cluster nodes
like literally what it says on the tin, no cap.
πΈ SYNOPSIS πΈ
fence_kdump_send [OPTIONS]... [NODE]...
π¦ DESCRIPTION π¦
so fence_kdump_send is a little utility whose whole job is sending messages that say "hey bestie, this node has entered the kdump crash recovery service". that's it. that's the gig. π
the way this is meant to work is: the fence_kdump agent uses these messages as its way of detecting that a failed node has entered the kdump crash recovery service. iykyk.
the fence_kdump_send utility is typically run from inside the kdump kernel, after a cluster node has hit a kernel panic π. once the cluster node has entered the kdump crash recovery service, fence_kdump_send will periodically send messages to all the cluster nodes. and when the fence_kdump agent receives a valid message from the failed node β boom, fencing is complete. slay. β¨
π OPTIONS π
-p,--ipport=PORTβ the IP port number that thefence_kdumpagent is listening on for messages. (default:7410)-f,--family=FAMILYβ the IP network family. this one forcesfence_kdump_sendto use one particular network family, no vibes-based guessing. the value for FAMILY can be"auto","ipv4", or"ipv6". (default:auto)-c,--count=COUNTβ how many messages to send. and listen β if COUNT is0,fence_kdump_sendwill just send messages indefinitely. forever. she does not stop. π (default:0)-i,--interval=INTERVALβ the time to wait between sending a message. the value for INTERVAL must be greater than zero, okay? zero is not the move here. (default:10)-v,--verboseβ print verbose output. more words, more info, we love her for it π-V,--versionβ print version and exit. short and sweet.-h,--helpβ print usage and exit. the classic. the icon.
fr fr, do not sleep on -i β that value has to be greater than zero or we're not doing anything.
π AUTHOR π
Ryan O'Hara <rohara@redhat.com>
(the literal main character of this manpage, we stan π«Ά)
π SEE ALSO π
fence_kdump(8), mkdumprd(8), kdump.conf(5)
go read those next bestie, they're all connected, it's giving lore π§
okay that's the whole page!! thanks for reading, mwah π this was fence_kdump_send(8) out of the System Manager's Manual, and yes she ate. periodt. π
β¨π
π¦ where this page comes from
- centos-stream 10: fence-agents-kdump 4.16.0-36.el10 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- centos-stream 9: fence-agents-kdump 4.10.0-124.el9 Β· GPLv2+ and LGPLv2+
- debian bookworm: fence-agents 4.12.1-1 Β· GPL-2.0-or-later
- debian trixie: fence-agents-kdump 4.16.0-3 Β· GPL-2.0-or-later
- fedora 43: fence-agents-kdump 4.16.0-5.fc43 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- fedora 43: fence-agents-kdump 4.17.0-1.fc43 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- fedora 44: fence-agents-kdump 4.17.0-2.fc44 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: fence-agents-kdump 4.16.0+git.1750325058.755815b1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: fence-agents-kdump 4.16.0+git.1750325058.755815b1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: fence-agents-kdump 4.16.0+git.1750325058.755815b1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- opensuse-leap 16.0: fence-agents-kdump 4.16.0+git.1750325058.755815b1-160000.2.2 Β· GPL-2.0-or-later AND LGPL-2.0-or-later
- ubuntu jammy: fence-agents-extra 4.7.1-1ubuntu8 Β· GPL-2.0-or-later
- ubuntu jammy: fence-agents-extra 4.7.1-1ubuntu8.1 Β· GPL-2.0-or-later
- ubuntu noble: fence-agents-kdump 4.12.1-2~exp1ubuntu4 Β· GPL-2.0-or-later
- ubuntu questing: fence-agents-kdump 4.16.0-3ubuntu1
- ubuntu resolute: fence-agents-kdump 4.17.0-1ubuntu1 Β· GPL-2.0-or-later
- ubuntu stonking: fence-agents-kdump 4.17.0-1ubuntu2 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms