-
Notifications
You must be signed in to change notification settings - Fork 648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wazuh service does not run together with Caddy #4321
Comments
My first hunch is overlapping ports. Do |
Looks more like it fails scanning the port and crashes itself by mere fact of being suddenly connected to caddy... |
The plugin is a Wazuh agent. Not the server which does indeed require ports 80 and 443 amongst others. |
Installing the wazuh agent the first time reveals some more issues under the hood: Template does not render:
And some validation thats too strict on first install so the migration fails:
Probably unrelated but I just wanted to add it here. Seems like a small cleanup of that plugin could be needed sometime. |
I won't be able to troubleshoot this in combination with caddy since I do not have a wazuh collection endpoint and the service will not start when I do not specify a valid one. So I can't be of much use. If it is indeed related to caddy though, please give me another ping so I can ask around. |
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
Wazuh agent will not start completely due to wazuh-modulesd quitting after start with an "Illegal Instruction"
Clean install of version 1.0 and later version 1.1 of the plugin
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Wazuh service should run.
Screenshots
*** With caddy running ***
*** With caddy stopped ***
Relevant log files
dmesg reports:
pid 13670 (wazuh-modulesd), jid 0, uid 0: exited on signal 4 (no core dump - bad address)
Additional context
Add any other context about the problem here.
Environment
OPNsense 24.7.7-amd64
os-caddy (installed) 1.7.3
os-wazuh-agent (installed) 1.1
The text was updated successfully, but these errors were encountered: