Can you please help me debug this one

[Neil Roña]

{"title": "Wazuh Internal Error", "detail": "Some Wazuh daemons are not ready yet in node \"node01\" (wazuh-modulesd->restarting, wazuh-analysisd->restarting, wazuh-execd->restarting, wazuh-db->restarting, wazuh-remoted->restarting)", "dapi_errors": {"node01": {"error": "Some Wazuh daemons are not ready yet in node \"node01\" (wazuh-modulesd->restarting, wazuh-analysisd->restarting, wazuh-execd->restarting, wazuh-db->restarting, wazuh-remoted->restarting)", "logfile": "WAZUH_HOME/logs/api.log"}}, "error": 

unable to log to wazuh due to internal error

[hasitha.u...@wazuh.com]

Hi Neil

Please allow me some time; I’m currently looking into this and will get back to you with an update as soon as possible.

[hasitha.u...@wazuh.com]

Hi Neil,

This error usually means the dashboard can reach the Wazuh API, but the API is reporting that the manager is not ready because several core daemons on node01 are restarting, such as wazuh-analysisd, wazuh-remoted, wazuh-execd, wazuh-db, and wazuh-modulesd. So this is generally a manager-side issue, not just a dashboard login issue.

I would start with these checks on the Wazuh manager node:

systemctl status wazuh-manager
/var/ossec/bin/wazuh-control status

Wazuh documents both the manager service check and the wazuh-control status command for confirming which daemons are actually running.

Then check the internal logs, especially:
cat /var/ossec/logs/ossec.log | grep -i -E "error|warn|crit"

If the API itself is down, we recommend restarting the manager and verifying the API again:

systemctl restart wazuh-manager

That is the documented first step when the API on port 55000 is unavailable.

Also, check basic system resources, because Wazuh community troubleshooting for this exact “daemons are not ready yet” error commonly points to resource issues, daemon/configuration issues, or other underlying system problems:

df -h
free -h

This is especially worth checking when several daemons are restarting at the same time.

If a restart only fixes it for a short time, my next suspicion would be an underlying manager problem rather than the dashboard itself
For example, something causing one daemon to fail and the rest to stay unready. The fastest way to confirm that is by looking at the first errors in ossec.log right after the manager starts.

Let me know the update on this so we can check further.

[Neil Roña]

/var/ossec/bin/wazuh-control status

wazuh-clusterd not running...

wazuh-modulesd is running...

wazuh-monitord is running...

wazuh-logcollector is running...

wazuh-remoted is running...

wazuh-syscheckd is running...

wazuh-analysisd is running...

wazuh-maild is running...

wazuh-execd is running...

wazuh-db is running...

wazuh-authd is running...

wazuh-agentlessd not running...

wazuh-integratord not running...

wazuh-dbd not running...

wazuh-csyslogd not running...

wazuh-apid is running...

Api is up as well as the manager is running

[Neil Roña]

I restarted the manager several times but still the same

[hasitha.u...@wazuh.com]

Hi Neil,

As discussed, let's fix one issue at a time. Please allow me sometime I will check and update asap.

[Neil Roña]

Hi ,

This is okay already, we created new wazuh instance and then migrated all data to it