[BUG] After upgrade to 4.9.0-1 (debian12) stuck with "Response Error" in log and "Wazuh dashboard server is not ready yet" #292
Comments
|
Hm, just added the netstat output. |
|
9200 and 9300 is tied to the indexer rather than the dashboard, or? |
|
Did the update too on Ubuntu 24.04.1 LTS , same error message |
|
I'm also having exact same issue and same messages. I have Ubuntu 22.04.4 LTS and did apt-get upgrade Some log files cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn" cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn" |
|
I also have the same problem after updating to version 4.9.0 on Ubuntu 22.04.4 LTS |
|
This command did the trick. Got answer from slack channel.
In all services in one server deployment, changing the password should solve the issue. |
|
in wazuh-cluster.log I had entries: Authentication finally failed for kibanaserver from 127.0.0.1:51086 I found: https://groups.google.com/g/wazuh/c/rdCF0MBR6oU It helped |
|
@kullarkert thank you for suggesting a solution, but I still have this error. The server was reset after the password was changed. |
|
Hi have problem after update Can help me Thanks |
|
As part of Wazuh 4.9.0, we published Wazuh dashboard revision 1 packages: These packages introduced a change in the keystore location to To resolve this, we have rolled out Wazuh dashboard revision 2 of these packages: Wazuh 4.x repositories are available again.
|
asteriscos
added
reporter/community
I can confirm that I was able to upgrade to 4.9.0 now without issue. Thanks for the fix. |
this is working for me. Thank you. |
|
No luck here. The error appeared after upgrading wazuh-dashboard from 4.8.2-1 to 4.9.0-2 and wazuh-indexer and wazuh-manager from 4.8.2-1 to 4.9.0-1. I stopped and started the three services in the recommended order and tried |
|
@genseirin can you please provide the output of these commands: Wazuh indexer
Wazuh dashboard
|
|
Hi @asteriscos journalctl -u wazuh-indexer | grep -iE "err|warn" Sep 13 10:23:38 WAZUH systemd-entrypoint[1201]: WARNING: A terminally deprecated method in java.lang.System has been called curl -k -u ':' https://127.0.0.1:9200/_cluster/health?pretty { journalctl -u wazuh-dashboard | grep -iE "err|warn" Sep 13 11:58:56 WAZUH opensearch-dashboards[23467]: {"type":"log","@timestamp":"2024-09-13T04:58:56Z","tags":["error","opensearch","data"],"pid":23467,"message":"[TimeoutError]: Request timed out"} [root@DCPAWAZUH ossec]# ls -la /usr/share/wazuh-dashboard/config/ ls -la /etc/wazuh-dashboard/ drwxr-x---. 3 wazuh-dashboard wazuh-dashboard 4096 Sep 13 10:37 . [root@DCPAWAZUH ossec]# cat /etc/default/wazuh-dashboard OSD_PATH_CONF="/etc/wazuh-dashboard" |
|
@asteriscos Thank you! Wazuh indexer
no output
Wazuh dashboard
|
asteriscos
added
level/task
@genseirin I see a couple of problems in the logs: CredentialsIf the curl to If you don't remember the credentials you can reset the password using this tool: Execute it https://documentation.wazuh.com/current/user-manual/user-administration/password-management.html kibana_3 indexI can see in the logs you have an issue with |
@Dara-cy what type of deployment do you have? is it an all-in-one installation or a distributed one? |
|
Was having these issues too, resetting all passwords and updating nodes did the trick for all but one warning message which I am investigating outside of this thread. Thanks! |
Thanks for solution. I solved with curl -k -XDELETE -u : https://:9200/.kibana_3` systemctl restart wazuh-dashboard |
|
Hi @asteriscos Actually it is an all in one installation, but have 2 ip interface that 10.84.54.51 ( for dashboard) and 10.84.55.5 ( for indexer and rsyslog server). It's running well before i upgrade. Now agent, rsyslog working and dashboard is not ready yet. Dashboard configserver.host: 0.0.0.0 opensearch.ssl.verificationMode: certificate Curl checkcurl -k -u 'admin:admin' https://127.0.1:9200/_cluster/health?pretty wazuh-dashboard statuswazuh-dashboard.service - wazuh-dashboard journalctl -u wazuh-dashboard | grep -iE "err|warn"(restart dashboard and index service) Sep 15 16:16:28 DCPAWAZUH01 opensearch-dashboards[91828]: {"type":"log","@timestamp":"2024-09-15T09:16:28Z","tags":["error","opensearch","data"],"pid":91828,"message":"[ConnectionError]: connect ECONNREFUSED 127.0.0.1:9200"} Thank you again help. |
|
Hi @asteriscos Run this fix my dashboard ''' But wazuh agent has connection error, I will check version or reinstall agent and notify everyone soon Many thanks |
Your solution was very helpful, thanks a lot! |
|
Hi @asteriscos "1. Install the new Wazuh dashboard revision 2 packages. Have a nice day :) |
|
Hi, I'm facing this problem too, but I'm not able to solve it yet. I updated Wazuh from 4.7.5 to 4.8.2 and then to 4.9.0. Now I am getting the error “Wazuh dashboard server is not ready yet”. Here is what I tried:
Here is the information about my system: Wazuh indexerWazuh dashboard(then the last line is repeated) |
|
@MAH69IK your problems seems to indicate a communication problem between dahsboard and indexer. On your message you said you changed the password in the keystore to be like the one stored in wazuh.yml but those files are not related, and do not require having the same password at all. To fix your deployment, I would follow the changing password documentation from https://documentation.wazuh.com/current/user-manual/user-administration/password-management.html |
Hi, after resetting the server, the problem with the message returned "Wazuh dashboard server is not ready yet". My Output: sudo cat /etc/default/wazuh-dashboard OSD_PATH_CONF="/etc/wazuh-dashboard" sudo systemctl restart wazuh-dashboard.service && sudo journalctl --since "$(date +"%F %T")" -fu wazuh-dashboard.service sudo systemctl status wazuh-indexer sudo lsof -i -nP | grep LISTEN | grep wazuh-indexer |
where are these packages? |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
I upgraded from 4.8 (4.8.2 I believe), following https://documentation.wazuh.com/current/upgrade-guide/upgrading-central-components.html
Steps to reproduce the behavior:
Expected behavior
OpenSearch Version
wazuh-indexer/now 4.9.0-1 amd64 [installed,local]
wazuh-manager/now 4.9.0-1 amd64 [installed,local]
Dashboards Version
wazuh-dashboard/now 4.9.0-1 amd64 [installed,local]
Plugins
Please list all plugins currently enabled.
Not sure how I find out. I think I run more or less "out of the box" installation.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
I have updated before. Started with a 4.7.x version, got through a couple of 4.8.x steps. All worked well previously following the instructions.
wazuh-manager and wazuh-indexer and wazuh-dashboard all show "active (running)" when asking systemctl status .
However, wazuh-dashboard fills the "log" (journalctl) with
Restarting wazuh-dashboard generates the following log-flow
Curl to the dashboard does not respond either.
Content of opensearch_dashboards.yml
netstat
The text was updated successfully, but these errors were encountered: