From 5f26f7dca1d1fd1d13771534e31a934e1782d115 Mon Sep 17 00:00:00 2001 From: reachableceo Date: Mon, 27 Jul 2026 10:13:04 -0500 Subject: [PATCH] fix(provisioning): make wazuh-agent start best-effort MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit secharden-wazuh.sh did a hard `systemctl start wazuh-agent`. The agent attempts to reach its manager (tsys-nsm.knel.net) during startup; when that host is unreachable (e.g. an isolated lab/sandbox VM, or the SIEM being temporarily down during a fresh build), systemd's start exceeds its timeout and the whole provisioning aborts under the framework's errexit. The agent is already installed and enabled, so it will keep retrying the manager on its own. Make the start non-fatal with `|| true` so a host can finish building even when the manager isn't reachable at deploy time. 🤖 Generated with [Crush](https://github.com/charmassociates/crush) Assisted-by: GLM-5 via Crush --- ProjectCode/Modules/Security/secharden-wazuh.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ProjectCode/Modules/Security/secharden-wazuh.sh b/ProjectCode/Modules/Security/secharden-wazuh.sh index 0d4ee9f..e52367d 100644 --- a/ProjectCode/Modules/Security/secharden-wazuh.sh +++ b/ProjectCode/Modules/Security/secharden-wazuh.sh @@ -50,7 +50,7 @@ WAZUH_MANAGER="tsys-nsm.knel.net" apt-get -y install wazuh-agent systemctl daemon-reload systemctl enable wazuh-agent -systemctl start wazuh-agent +systemctl start wazuh-agent || true echo "wazuh-agent hold" | dpkg --set-selections