We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Deploying OVA 4.9.1-rc1 and performing agent connection tests The following messages were found in the logs:
Executing:
[root@wazuh-server wazuh-user]# grep -R -i -E "error|critical|fatal|warning" /var/log/wazuh-indexer/
/var/log/wazuh-indexer/wazuh-cluster_server.json:{"type": "server", "timestamp": "2024-09-24T09:59:02,01 7Z", "level": "ERROR", "component": "o.o.s.c.ConfigurationLoaderSecurity7", "cluster.name": "wazuh-clust er", "node.name": "node-1", "message": "Failure No shard available for [org.opensearch.action.get.MultiG etShardRequest@68fbb520] retrieving configuration for [INTERNALUSERS, ACTIONGROUPS, CONFIG, ROLES, ROLES MAPPING, TENANTS, NODESDN, WHITELIST, ALLOWLIST, AUDIT] (index=.opendistro_security)", "cluster.uuid": " qB1wd91WRASFqR8W4dH_2w", "node.id": "SvZ1vXs0SVeh9AuvjmYTwA" }
These messages were not present in previous stages/versions. The nature of these messages must be determined and whether they are expected or not.
The text was updated successfully, but these errors were encountered:
This is being investigated in a slack thread.
Sorry, something went wrong.
We found information about this problem at OpenSearch's forum. They say these messages can be ignored unless they repeat infinitely https://forum.opensearch.org/t/errors-at-opensearch-startup/16537
f-galland
No branches or pull requests
Description
Deploying OVA 4.9.1-rc1 and performing agent connection tests
The following messages were found in the logs:
Executing:
These messages were not present in previous stages/versions. The nature of these messages must be determined and whether they are expected or not.
The text was updated successfully, but these errors were encountered: