-
Notifications
You must be signed in to change notification settings - Fork 22
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] Installation of indexer fails #269
Comments
The output after applying CIS build script Server L1:
|
Hi @HachimanSec The error cause is: Jun 14 12:12:03 wazuh-main systemd-entrypoint[37534]: fatal error in thread [main], exiting
Jun 14 12:12:03 wazuh-main systemd-entrypoint[37534]: java.lang.NoClassDefFoundError: Could not initialize class com.sun.jna.Native
Jun 14 12:12:03 wazuh-main systemd-entrypoint[37534]: Caused by: java.lang.ExceptionInInitializerError: Exception java.lang.UnsatisfiedLinkError: /tmp/opensearch-12518441532525806421/jna14463842273615614935.tmp: /tmp/opensearch-12518441532525806421/jna14463842273615614935.tmp: failed to map segment from shared object [in thread "main"] We have experienced problems during the installation of Wazuh Indexer if the Operative System has the The warnings messages are known and expected, there is nothing wrong there. |
Closed due to inactivity. |
This was my exact problem, as the server was pre-hardened, all of the tmp filesystems have nodev,noexec flags on mount. |
We are working on that on #501 |
Describe the bug
Installation via
sudo bash wazuh-install.sh -a
fails at installation of the Indexer.The error in journalctl is:
journalctl.log
wazuh-install.log
It seems to be somewhat similiar to wazuh/wazuh#22122 - but I haven't found a solution there.
To Reproduce
Steps to reproduce the behavior:
Call
sudo bash wazuh-install.sh -a
on Ubuntu 22.04Latest apt update and upgrade has been done.
Expected behavior
An all in one installation as described here: https://documentation.wazuh.com/current/quickstart.html
Plugins
Screenshots
Host/Environment (please complete the following information):
Additional context
I also posted on Slack to see if anyone experienced this https://wazuh.slack.com/archives/C0A933R8E/p1718361281257639
EDIT 2❗Executing CIS Build Script L1 Server kills the wazuh-indexer with the described error.
EDIT 1 ❗It appears that the problem occurs once the CIS Build script has been executed.
I have setup a new Ubuntu 20.04 server and installed the all-in-one package. It worked.
After I executed the build script from CIS for server L2 the indexer fails to start.
The text was updated successfully, but these errors were encountered: