fleet-wake

Wake a sleeping fleet node by applying three escalation strategies in order: health check probing, SSH caffeinate commands, and Wake-on-LAN packets. This ensures the node becomes responsive and ready to receive tasks before you dispatch work to it.

Automating machine wake-ups in heterogeneous environments is best handled by a multi-strategy escalation approach. It tries health checks, SSH caffeinate, and Wake-on-LAN sequentially to maximize success rates across diverse hardware and network configurations where a single method might fail.

Wake-on-LAN is used as the final escalation strategy for unresponsive fleet nodes. After health probing and SSH caffeinate fail, WoL packets are sent to wake the machine, allowing the Fleet Nerve daemon to restart, resume heartbeats, and deliver queued messages.

You can use SSH caffeinate to wake an idle remote machine during long-running jobs. This remote command execution strategy is attempted if the initial health check fails, ensuring the node remains productive without interrupting ongoing fleet operations.

After a fleet node wakes up, the Fleet Nerve daemon starts automatically, which resumes heartbeat signals and delivers queued messages. This post-wake workflow ensures no tasks are lost and the node is fully ready to receive new dispatches.

Relying on a single Wake-on-LAN packet is insufficient in heterogeneous fleet environments where network configurations or hardware states vary. A three-strategy escalation that includes health checks and SSH caffeinate handles edge cases where WoL packets alone might fail to reach the target node.