mirror of
https://github.com/Security-Onion-Solutions/securityonion.git
synced 2026-11-18 18:16:02 +01:00
A push dispatched seconds after a salt-master restart was lost: minions rejoin the new publisher on a randomized ZeroMQ reconnect delay (up to ~22s with the default recon_default/recon_max), and a job published before then reaches nobody. The orchestration's refresh_pillar step timed out with "No minions responded", the drainer logged "push failed" as an ERROR, and so-log-check failed the run. Seen on a standalone 3.5.0 install: a highstate restarted salt-master (new reactor/engine config), the drainer dispatched a soc push 8s later, and the job cache shows the refresh_pillar job matched the minion but got no return. Measured on the same host over five restarts, jobs published in the first 4-9s were lost every time. The drainer now leaves ready intents in place for a later pass while /var/run/salt-master.pid is less than 45s old. On a multi-node grid this also avoids a batch state run silently skipping the minions that have not reconnected yet, since batch only sends the job to minions that answer its ping.