Wazuh docker: internal server error after upgrading vom 4.10.0 to 4.10.1

129 views
Skip to first unread message

Chris Schneider

unread,
Feb 10, 2025, 9:55:52 AMFeb 10
to Wazuh | Mailing List
Hi,

I have upgraded my docker containers from 4.10.0 to 4.10.1 and get this error after logging into the dashboard. What am I doing wrong?


Version: 2.16.0 Build: 410101 Error: Internal Server Error HttpFetchError@https://192.168.60.9:5601/410101/bundles/core/core.entry.js:15:277615 fetchResponse@https://192.168.60.9:5601/410101/bundles/core/core.entry.js:15:285061 


wazuh_dashboard_error.png


thank you,
Chris

Chris Schneider

unread,
Feb 10, 2025, 10:08:55 AMFeb 10
to Wazuh | Mailing List
Update:

After login out, I cannot login again. -> Invalid username or password.

This is an entry from the dashboard container logs:

Failed authentication: Error: [circuit_breaking_exception] [parent] Data too large, data for [<http_request>] would be [1039665744/991.5mb], which is larger than the limit of [1020054732/972.7mb], real usage: [1039665744/991.5mb], new bytes reserved: [0/0b], usages [request=0/0b, fielddata=0/0b, in_flight_requests=0/0b], with { bytes_wanted=1039665744 & bytes_limit=1020054732 & durability="TRANSIENT" } | type=log @timestamp=2025-02-10T15:07:47Z tags=["error","plugins","securityDashboards"] pid=54


Olusegun Adenrele Oyebo

unread,
Feb 10, 2025, 12:16:29 PMFeb 10
to Wazuh | Mailing List
Hello Chris,

As you can see from the logs, you have reached a circuit breakage exception, and you'll need to increase the Wazuh indexer heap size to improve the performance of your Wazuh indexer. The circuit_breaking_exception is a mechanism used to prevent operations from causing an OutOfMemoryError. It seems like wazuh-indexer was using most of the JVM heap configured, and the total memory required for all operations was superior to the memory available.

Enter the indexer container and edit the jvm.options file. To confirm the ID of your indexer container, run the command docker ps. For example, to enter the container:
  •  docker exec -it --user root single-node-wazuh.indexer-1 bash
Edit the jvm.options file to increase the JVM heap size. The recommended value is half of the system RAM. For example, set the size as follows for a system with 8 GB of RAM (reference):
-Xms4g
-Xmx4g

Where the total heap space:
-Xms4g - initial size is set to 4Gb of RAM.
-Xmx4g - maximum size is to 4Gb of RAM

Restart the Wazuh indexer and dashboard containers:
  • docker restart single-node-wazuh.indexer-1
  • docker restart single-node-wazuh.dashboard-1
Let me know if this resolves the issue.

Best regards.
Reply all
Reply to author
Forward
0 new messages