INFO: Updating the internal users.
INFO: passwords_getNetworkHost IP: “0.0.0.0”
<Multiple Stars>
This tool will be deprecated in the next major release of OpenSearch
https://github.com/opensearch-project/security/issues/1755
<Multiple Stars>
Security Admin v7
Will connect to localhost:9200
ERR: Seems there is no OpenSearch running on localhost:9200 – Will exit
cp: cannot stat “/etc/wazuh-indexer/backup/internal_users.yml”
chmod: cannot access ‘/etc/wazuh-indexer/internal-users-backup/internal_users_20251201_141719.yml.bkp
My question is there any way to start Opensearch early"? Or is there a way to make this backup manually so I can bypass this step.
Thank you for your help.
Hello Paul,
Thanks for reporting this.
To help you best, I need a little more context about your setup. Could you please answer the following questions:
What type of deployment are you using?
What exact command(s) did you run to change the password?
Please include the full command line (including any flags), and indicate whether you ran it manually or as part of a custom script / automation pipeline.
At the time you ran the password tool, was the indexer (OpenSearch / Wazuh Indexer) already running and healthy?
You can run this to check:
sudo systemctl status wazuh-indexer
If this is part of a deployment automation/custom script, what is the order of steps?
When do you start the indexer service relative to when the password change command runs?
What Wazuh version are you using?
Are you running the script as root?