-
Notifications
You must be signed in to change notification settings - Fork 99
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
Warning and error logs found in wazuh-indexer in demo environment #1511
Comments
I was researching this error message, it is because the SSLv3 protocol is considered insecure, so it is directly disabled in the JDK. https://www.oracle.com/java/technologies/javase/instructions-to-mitigate-the-ssl-v30-vulnerability.html Regarding the Indexer configuration, we have the same default configuration as opensearch, that is, we do not set the protocol to use to be SSLv3, so in the future, we could investigate the forced use of TLS and apply it in our configuration as default. I could not find the logs again or generate this SSLv3 event again, so probably at some point the nodes try to use this protocol and since it is blocked, it continues with another, I could not verify this, but the application continues to work for which I do not consider it critical and I think that the investigation can be advanced in the next release |
These options have been added and tested to resolve this error:
It seems to be resolved. The logs will be checked again tomorrow. |
We need to modify the SG disallowing the public 9200 access and deploy/run the test over a deployment VM. |
Some tasks to copy the python tests scripts were created. The use cases tests playbook is being modified to be executed from the First indexer node. |
The copy task were improved to reduce the execution time. |
Finally the previous changes were reverted and a new branch ( |
I am reopening this because this error keeps popping up in each
|
I have been analyzing this error message:
|
A test enabling |
TestI performed the test:
[2022-11-08T18:56:21,349][ERROR][o.o.s.a.s.SinkProvider ] [node-1] Default endpoint could not be created, auditlog will not work properly.
[2022-11-08T18:59:08,786][ERROR][o.o.s.a.s.SinkProvider ] [node-1] Default endpoint could not be created, auditlog will not work properly. ConclusionThe error is related to the |
We might open an issue in the Opensearch repository. I will change the status to |
Some error logs were found in wazuh/wazuh-qa#2819 (comment) and we created #1489. These logs continue to appear, but in addition, these new warnings have been found:
systemctl status wazuh-indexer -l
:These logs have been found on all machines with wazuh-indexer (bootstrap, master b, master c, and dashboard).
egrep -i "ERROR|WARNING" /var/log/wazuh-indexer/wazuh.log
:The text was updated successfully, but these errors were encountered: