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

Investigate the need of increase TimeoutStartSec in wazuh-indexer service #1919

Open
5 tasks
alberpilot opened this issue Nov 2, 2022 · 0 comments
Open
5 tasks

Comments

@alberpilot
Copy link
Contributor

Wazuh version Install type Action performed Platform
4.3.9-1 Wazuh indexer Start Deb/RPM

An error was reported starting the Wazuh indexer:

job for wazuh-indexer.service failed because a timeout was exceeded

This is commonly due to not enough host resources (either not enough total CPU/RAM or available CPU/RAM). The service tries to start the process but this one is taking longer than foreseen.

The service variable TimeoutStartSec determines the timeout of starting the process. Increasing this value could allow starting the service in those hosts with resource limitations.

Tasks

  • Determine why the current value was set to 75.
  • Investigate Opensearch and Elasticsearch values.
  • Investigate the pros/cons of increasing this value.
  • If the investigation concludes with increasing value, change the code.
  • Test with the older package and limited host, reproducing the error. Then, test the new one that results in a started service.
@snaow snaow added this to the Release 4.5.0 milestone Nov 16, 2022
@snaow snaow removed this from the Release 4.5.0 milestone Dec 21, 2022
@teddytpc1 teddytpc1 added level/task Subtask issue type/enhancement Enhancement issue labels May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants