Wazuh-indexer Error: Not yet initialized (you may need to run securityadmin)

[DaniTC]

Good afternoon,

I am having this error. I am currently on version 4.4.0 and when my Centos7 OVA is updated to version 4.4.1 I get the error indicated in the subject and I cannot access the panel.

What I can do? Everything was working fine until the new version was updated.

Thank you.

[Federico Gustavo Caffieri]

Hello DaniTC,

In order to help you with your query, I would need you to send me the following information:
- Could you execute the following command and send the result?
system status wazuh-indexer

- Please send the result of the following command
grep -i -E -R "error|critical|fatal|warning" /var/log/wazuh-indexer/

 
- Could you tell me which guide or steps you used to update the OVA? 

[DaniTC]

Good morning Frederick,

The OVA I have since version 4.3 has been working without problems. All wazuh and system packages have been updated automatically and have worked well.

Wazuh was in version 4.4.0 working fine and when updating the system only to 4.4.1 is when it has broken.

I attach the captures of the errors that you have asked me.

I am waiting for your help.

Thank you

[Federico Gustavo Caffieri]

Hello DaniTC,

According to the errors that are displayed in the logs, it seems that the Wazuh indexer cluster needs to be initialized.
To do this you must execute the following command:
/usr/share/wazuh-indexer/bin/indexer-security-init.sh

I leave you the section of the documentation where you will find this command and how to validate that it started correctly.
https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/step-by-step.html#cluster-initialization

I ask you if you can share the steps you have followed to update your OVA from 4.4.0 to 4.4.1 in order to replicate the problem in a local environment and be able to better assist you.