Hello
Chris,
According to your Wazuh Dashboard issues seem to be linked to the following:
wazuh-modulesd->failed: This daemon handles important Wazuh modules like Syscollector and Vulnerability Detector. If it's failing, it could indicate a configuration problem or an internal error.
Error 3099: This means some essential Wazuh services, like wazuh-modulesd, are not running properly on the node (wazuh-manager-master). If these key components aren’t active, the API won’t be able to connect as expected.
To troubleshoot further, please provide the output of the following commands:
cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i -E "error|warn"
cat /var/ossec/logs/ossec.log | grep -i -E "error|warn"
journalctl -xeu wazuh-dashboard
cat /usr/share/wazuh-dashboard/data/wazuh/logs/wazuhapp.log | grep -i -E "error|warn"
cat /var/log/filebeat/filebeat | grep -i -E "error|warn" And also try to restart pods.
If this still persist provide me the details of resources.
For example: Ram, CPU and Hard disk.
Ref:
https://documentation.wazuh.com/current/user-manual/wazuh-dashboard/troubleshooting.htmlLet me know the results!
Regards,
Hasitha Upekshitha