Wazuh dashboard server is not ready yet

[Sam Heuchert]

Hi there!

For the last 2 weeks, I've been running into an issue where upon every reboot of my all in one, 4.3.5 instance of Wazuh in a Ubuntu VM, I am getting the "Wazuh dashboard server is not ready yet" after reboot.  Only after a restart of the "wazuh-indexer" -> "wazuh-dashboard" -> "wazuh-manager" services (in that order) am I able to hit the web UI.

Is this a known bug?

Thanks!

[Mauro Agustín Malara]

Hi!

Thanks for using Wazuh!

When you start the services in a different way than the one you mention, does the user interface work after a certain time?

----

I was testing this behavior you describe, but actually what happens is that the wazuh-dashboard component is waiting for wazuh-indexer to finish its initialization (which takes several seconds).

You can check it as follows:

1. Stop all services (wazuh-dashboard, wazuh-indexer, wazuh-manager).

2. Keep track of the dashboard and indexer logs: tail -F /var/log/wazuh-indexer/wazuh-indexer-cluster_server.json | egrep -iE 'Node.*initialized",' and tail -F /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log

3. Start all services (the last component to start should be the indexer).

4. You will see that when the following message appears in the indexer log:

   {"type": "server", "timestamp": "2022-07-18T13:04:31,610-03:00", "level": "INFO", "component": "o.o.s.c.ConfigurationRepository", "cluster.name": "wazuh-indexer-cluster", "node.name": "node-1", "message": "Node 'node-1' initialized", "cluster.uuid": "weclDmM_R4yw9UaNfKQrBA", "node.id": "lOXIzr6DQz28p3KYRPeKFg"  }
   

   the following messages will automatically be written to the dashboard log:

   {"date":"2022-07-18T16:04:34.911Z","level":"info","location":"initialize","message":"Wazuh dashboard index: .kibana"}
   {"date":"2022-07-18T16:04:34.912Z","level":"info","location":"initialize","message":"App revision: 4306"}
   {"date":"2022-07-18T16:04:34.912Z","level":"info","location":"initialize","message":"Total RAM: 7822MB"}
   

5. In your browser verify that the dashboard does not allow you to enter the UI for a few seconds (‘Wazuh dashboard is not ready yet’) until the message, mentioned above, appears in the log of the wazuh-indexer.

​

So, that is the expected behavior.

Let me know if you have any questions,

Regards.

[Sam Heuchert]

Thanks!  I will give it a look!