-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Occasional API timeouts #8544
Comments
Issue updateHey team! While working on issue #8541 (comment) to improve some error messages, I have seen that the API timeout errors already contain which endpoint has been executed and its parameters, like it can be seen in the last line of this log:
However, although the issue specification does not show the complete error trace (it was reported by a user), it turns out that the endpoint name/parameters are never displayed in its case. It is as if the API had gone into an infinite loop. Also, it seems to return a timeout despite using the Regards, |
I face a similar issue.
Hanging requests stay until wazuh-manager.service is restarted:
The wazuh-kibana-webapp logs out users after the API-Timeout (20000ms) with an anoying SESSION_EXPIRED, even if the user has just logged in. Error from the api.log on the wazuh master:
|
any update on this issue? |
Description
A community user is reporting API timeouts when accessing Kibana.
We first discarded any heavy CPU load issues as the server running Wazuh didn't exceed a huge load either when receiving a timeout nor the rest of the time. The manager is hosted at an AWS EC2 instance with 2 CPUs and 8 GB RAM. It is supporting ~100 agents.
Restarting the manager only recovers the API for a short time.
The size of
client.keys
, the number of files in/var/ossec/queue/db
and/var/ossec/queue/agent-groups
are acceptable (either match or are close to the actual number of agents).We tried to execute some curl requests directly to the API, but we received a timeout even we explicitly added the
wait_for_complete
parameter to the call.It returned:
Looking at the logs under
/var/ossec/log/api.log
we could see the following error showing up repeatedly:Please, feel free to request any further information regarding this issue.
Notes
The text was updated successfully, but these errors were encountered: