-
Notifications
You must be signed in to change notification settings - Fork 96
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
Infinite loop when running indexer-security-init.sh #1885
Comments
After some tests over wazuh-indexer package in CentOS 7 and Ubuntu 20 systems. It seems impossible to reproduce and such problem is related to Security admin and indexer deep code. We can't fix this problem at this development stage. |
This occurs on RHEL9 too. Just follow the assistant according to the docs, and create an Indexer cluster with at least 2 nodes. It is easy to reproduce. But when you use just one node, the cluster start succeeds. The issue seems like somewhere in Indexer cluster discovery. |
At the moment I was trying to reproduce the problem without success in Centos 7 and in Redhat 9, both in single node and in cluster, I will continue testing |
Hi. In my case, it was my problem. I did skip firewall configuration. And that blocked cluster discovery. But I do not know for the other use cases. |
A related discussion: #1776 |
Update reportResearch
Testing
Next steps
|
Update reportTesting multi-node deployment with and without firewallMulti node deployment - CentOS 7 - CentOS 9 Stream - no firewallCentOS 7 - Install Wazuh indexer - node-1
CentOS 9 Stream - Install Wazuh indexer - node-2
Initialize cluster - node-1
CentOS 9 Stream - Firewall enabled - 9200
CentOS 9 Stream - Firewall enabled - 9200 and 9300
CentOS 9 Stream - Firewall enabled - 9200 and 9400
CentOS 7 - Firewall enabled - 9200
CentOS 7 - Firewall enabled - 9300
CentOS 7 - Firewall enabled - 9400
Testing multi-node deployment modifying opensearch.yml configurationCentOS 7 - Node 1CentOS 7 - Wrong IP
CentOS 7 - Invalid IP
CentOS 7 - Correct configuration but failed service (no reboot)
CentOS 7 - Correct configuration and running service
CentOS 7 - typo in opensearch config (plugins.security.ssl.http.spemtrustedcas_filepath:)
CentOS 9 Stream - Node 2Wrong IP
Invalid IP
Testing custom Wazuh installation assistant multi-node deployment with 4.4.0 Wazuh indexer - CentOS 7 and Red Hat 9Wazuh indexer 4.4.0 - With firewalld and iptables disabled
Wazuh indexer 4.4.0 - With firewalld disabled and iptables enabled REJECT 9300
|
Update reportTestingWazuh indexer 4.4.0 - CentOS 7 - Red Hat 7 - Same procedure as Wazuh indexer 4.3.9
Messages appear every 30 seconds of execution
The same procedure has been carried out in an OpenSearch multi-node deployment, where the same result has been obtained. OpenSearch 2.3.0 - CentOS 7 - Red Hat 7 - Same procedure as Wazuh indexer 4.3.9 and 4.4.0CentOS 7 - Node 1 configuration
Red Hat 9 - Node 2 configuration
Wazuh indexer 4.4.0 - CentOS 7 - Red Hat 7 - Cluster start without Wazuh indexer wrapper
OpenSearch 1.2.0 - CentOS 7 - Red Hat 7 - Cluster start
|
Thanks, @rauldpm for the clarification. |
Description
When trying to execute the
indexer-security-init.sh
script and getting an error (probably due to configuration), if the configuration is modified and thewazuh-indexer
service is restarted again, it remains in an infinite loop executingindexer-security-init.sh
all the time, leaving the terminal unusable.Steps to reproduce
/etc/wazuh-indexer/opensearch.yml
file with an incorrect configuration (e.g. not setting thenetwork.host
correctly)indexer-security-init.sh
and receive the following error:/etc/wazuh-indexer/opensearch.yml
file with an correct configuration (e.g. setting thenetwork.host
correctly)systemctl restart wazuh-indexer
Result
The following message is displayed in an infinite loop, making it impossible to use the terminal:
The text was updated successfully, but these errors were encountered: