Skip to content
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 dashboard server is not ready yet #705

Open
reteinformatica opened this issue Feb 20, 2025 · 0 comments
Open

Wazuh dashboard server is not ready yet #705

reteinformatica opened this issue Feb 20, 2025 · 0 comments
Labels
level/task Task issue reporter/community Issue reported by the community type/bug Bug issue

Comments

@reteinformatica
Copy link

reteinformatica commented Feb 20, 2025

Hello everyone and thank you for your interest in my problem.
I installed Wazuh for the first time in a server with Ubuntu Server 20.04 and everything went well. The problem arose after rebooting the server. Trying to access the dashboard with the browser I get this error: 'Wazuh dashboard server is not ready yet'.
I did some research and investigating a bit I realized that the 'wazuh-indexer' service does not start. This is the result of the command 'systemctl status wazuh-indexer':

**wazuh-indexer.service - wazuh-indexer
Loaded: loaded (/lib/systemd/system/wazuh-indexer.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2025-02-18 20:20:05 UTC; 1 day 23h ago
Docs: https://documentation.wazuh.com
Main PID: 3427 (code=exited, status=1/FAILURE)

Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: Error: Could not create the Java Virtual Machine.
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: Error: A fatal exception has occurred. Program will exit.
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: at org.opensearch.tools.launchers.JvmErgonomics.flagsFinal(JvmErgonomics.java:125)
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: at org.opensearch.tools.launchers.JvmErgonomics.finalJvmOptions(JvmErgonomics.java:87)
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: at org.opensearch.tools.launchers.JvmErgonomics.choose(JvmErgonomics.java:70)
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: at org.opensearch.tools.launchers.JvmOptionsParser.jvmOptions(JvmOptionsParser.java:150)
Feb 18 20:20:05 vpnsvr systemd-entrypoint[3547]: at org.opensearch.tools.launchers.JvmOptionsParser.main(JvmOptionsParser.java:108)
Feb 18 20:20:05 vpnsvr systemd[1]: wazuh-indexer.service: Main process exited, code=exited, status=1/FAILURE
Feb 18 20:20:05 vpnsvr systemd[1]: wazuh-indexer.service: Failed with result 'exit-code'.
Feb 18 20:20:05 vpnsvr systemd[1]: Failed to start wazuh-indexer.**

And this is the result of the command 'systemctl start wazuh-indexer':

Job for wazuh-indexer.service failed because the control process exited with error code.
See "systemctl status wazuh-indexer.service" and "journalctl -xe" for details.

While the command 'journalctl -xe' shows this:

Feb 20 19:50:51 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:50:51Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:50:54 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:50:54Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:50:56 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:50:56Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:50:59 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:50:59Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:01 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:01Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:04 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:04Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:06 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:06Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:09 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:09Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:11 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:11Z","tags":["error","opensearch","data"],"pid":805,"message":"[>
Feb 20 19:51:14 vpnsvr opensearch-dashboards[805]: {"type":"log","@timestamp":"2025-02-20T19:51:14Z","tags":["error","opensearch","data"],"pid":805,"message":"[>

I did a lot of research and did various tests, including the one described in the “Wazuh indexer tuning” manual at this address: https://documentation.wazuh.com/current/user-manual/wazuh-indexer/wazuh-indexer-tuning.html

I even tried all suggests in this thread: #201

But everything was useless and I don't know how to do it anymore. Thank you all.

@reteinformatica reteinformatica added level/task Task issue type/bug Bug issue labels Feb 20, 2025
@Dwordcito Dwordcito added the reporter/community Issue reported by the community label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue reporter/community Issue reported by the community type/bug Bug issue
Projects
None yet
Development

No branches or pull requests

2 participants