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

[BUG] Failure No shard available log was found in OVA testing #428

Closed
pro-akim opened this issue Sep 24, 2024 · 2 comments
Closed

[BUG] Failure No shard available log was found in OVA testing #428

pro-akim opened this issue Sep 24, 2024 · 2 comments
Assignees
Labels
level/task Task issue qa_known Issues that are already known by the QA team type/bug Bug issue

Comments

@pro-akim
Copy link
Member

Description

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.

@pro-akim pro-akim added level/task Task issue type/bug Bug issue labels Sep 24, 2024
@wazuhci wazuhci moved this to Triage in Release 4.9.1 Sep 24, 2024
@f-galland f-galland self-assigned this Sep 24, 2024
@wazuhci wazuhci moved this from Triage to In progress in Release 4.9.1 Sep 24, 2024
@f-galland
Copy link
Member

This is being investigated in a slack thread.

@wazuhci wazuhci moved this from In progress to Blocked in Release 4.9.1 Sep 25, 2024
@wazuhci wazuhci moved this from Blocked to In progress in Release 4.9.1 Sep 25, 2024
@AlexRuiz7
Copy link
Member

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

@wazuhci wazuhci moved this from In progress to Blocked in Release 4.9.1 Sep 25, 2024
@havidarou havidarou added the qa_known Issues that are already known by the QA team label Sep 26, 2024
@havidarou havidarou closed this as not planned Won't fix, can't repro, duplicate, stale Sep 26, 2024
@havidarou havidarou moved this from Blocked to Done in Release 4.9.1 Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue qa_known Issues that are already known by the QA team type/bug Bug issue
Projects
No open projects
Status: Done
Development

No branches or pull requests

4 participants