FAIL TO RESET PASSWORD

[Abdulrazack Shabani]

Hi Team, 

I haven't login to my wazuh dashboard for a long time, I am trying to reset my password but I am facing an error as per screenshot below.

Everthing seem to be run both wazuh dashboard, indexer and manager

[Nikhil Gurjar]

Hi Abdulrazack

Could you please confirm when you attempted to log in to the Wazuh dashboard via the browser and encountered the “username or password is not correct” error?

Additionally, to help us identify the root cause, please share the following details:

1. Check the status of the Wazuh components:

systemctl status wazuh-manager
filebeat test output
systemctl status wazuh-indexer
systemctl status wazuh-dashboard

2. Re-run the password tool with verbose output on the Indexer VM:

/usr/share/wazuh-indexer/plugins/opensearch-security/tools/wazuh-passwords-tool.sh -v -a

Looking forward to your feedback.

Best regards,
Nikhil

[Abdulrazack Shabani]

Hi Nikhil,

The dashboard was working before but now it display "Wazuh dashboard server is not ready yet",

 The indexer is down and display error below:

"

Job for wazuh-indexer.service failed because the control process exited with error code.                                                                  

See "systemctl status wazuh-indexer.service" and "journalctl -xeu wazuh-indexer.service" for details.
" 

I have attached all the screenshots as requested.

--
You received this message because you are subscribed to the Google Groups "Wazuh | Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wazuh+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wazuh/4ed9fc91-80a6-4bc8-8869-40a2863f2c41n%40googlegroups.com.

[Nikhil Gurjar]

Hi Abdulrazack

The dashboard message “Wazuh dashboard server is not ready yet” appears because the Wazuh Dashboard is trying to connect to the Wazuh Indexer, but the Indexer service is currently not running.

Have you made any recent changes? If so, have you tried restarting the wazuh-indexer service afterward?

Additionally, please run the command below and share the output here in text format.

cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -iE  'err|warn|fail|cri' | tail -n 200

Looking forward to your update.

Best regards,
Nikhil

[Nikhil Gurjar]

Hi Abdulrazack

Thank you for sharing the logs. Unfortunately, the provided logs do not contain enough information to determine the root cause. Could you please share the complete log file so that I can analyze it and identify why the wazuh-indexer service is not starting after the restart?

Additionally, please provide the output of the following commands:

df -h
free -h
cat /etc/wazuh-indexer/jvm.options | grep -iE 'xm'

Looking forward to your update.

Best regards,
Nikhil

[Nikhil Gurjar]

Hi Abdulrazack

Unfortunately, the information provided so far is not sufficient to identify the root cause. Could you please restart the Wazuh Indexer service using the following command:

systemctl restart wazuh-indexer

After restarting, kindly share the relevant log files in ZIP format. If attaching files is not permitted, you may either use the “Add attachment” option or open a second SSH session to the Wazuh Indexer VM and monitor the logs in real time using:

tail -f /var/log/wazuh-indexer/wazuh-cluster.log | grep -iE 'err|fail|cri'

For your reference, the wazuh-cluster.log file is particularly helpful in identifying the underlying cause of this issue.

Looking forward to your update. 

Best regards,
Nikhil