There are a few things one can look at. What amount of resources did you assign to your Wazuh indexer server?
Are you using an all-in-one deployment or distributed? You can check the below reference for information on the hardware requirements:
After confirming and making sure that your environment meets the above specification, and if the issue still persists, you can try to reconfigure the
TimeoutStartSec in the Wazuh indexer service. Run the command
systemctl edit --full wazuh-indexer.service and change
TimeoutStartSec=0, save the changes and restart the service with command
systemctl restart wazuh-indexer. With this setting, there will be no timeout settings for starting the service.
If issue still persists, kindly revert with the Wazuh indexer logs by running the below commands:
- cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn"
- journalctl -u wazuh-indexer