-
Notifications
You must be signed in to change notification settings - Fork 25
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
[BUG] 4.9.1 initial startup of indexer fails due to noexec filesystems from STIG compliance + workaround #501
Comments
Hello @IKatsu I assume you refer to this other issue. We'll revisit the problem. It's good to know that the workaround works. We'll try to make that not necessary for users running wazuh-indexer under security hardened operating systems. |
That's the other issue I was referring to yes. |
This issue seems to be caused by the use of A potential solution is to store the |
Fix applied in PR #533 is currently under testing. This update does not utilize the While all the Linux-based OS tested so far have this tool pre-installed, we should analyze which OS might be incompatible with this implementation and the potential issues it could cause. |
I saw another report of the same thing that said fixed in 4.9.0 but I am getting the exact same error on 4.9.1.
As per STIG/DOD policy the following filesystems are 'noexec'
/var/log
/var/log/audit
/var/tmp
/tmp (although in my case we decided to NOT do /tmp due to some legacy shenanigans , so it failed with /tmp NOT being noexec)
To Reproduce
Install and try to start on STIG compliant machine.
Expected behavior
Successful starting on STIG compliant machine.
Host/Environment (please complete the following information):
Additional context
I can't use any of the provided automatic installation options so this was done via the step by step install documentation.
A slightly modified workaround from the older report works as a workaround:
The text was updated successfully, but these errors were encountered: