Closed awptechnologies closed 4 months ago
I know this is a terrible issue report. But it is never the same its always so random when it gives me errors and the errors it gives.
Here is another error AxiosError: timeout of 20000ms exceeded
Seems like i have lost all access to wazuh no matter how many times i refresh i now get a error 500 internal server error. Also i see this in container logs.
search_phase_execution_exception]: all shards failed | type=log @timestamp=2024-04-30T12:45:30Z tags=["error","opensearch","data"] pid=54
Figured it out on my own. After messing with it forever i finally said screw it and deleted the wazuh-indexer-data volume and everything is working again.
Hope This helps anyone out there running wazuh with nfs. A heck of a lot better to loose the previous data then redo the whole configuration especially when all the volumes are mapped to an nfs share.
Out of no where when signing in i get multiple errors sometimes internal server errors. Sometimes API errors. I refresh page multiple times. Sometimes it loads. Sometimes it says i don't have permission to view agents then sometimes it shows no agents at all. After refreshing multiple times and waiting a while all of a sudden page refreshes on its own and it works. It acts like some kind of data base error. I will attach all of the container logs below. FYI these volumes are stored on an NFS share. I'm not sure if that's the issue but i figured i would mention it.
_wazuh_manager.1.nsufhb10tgvxi2lnwj13d5bmn_logs.txt _wazuh_indexer.1.2gr87v02iuj1u5805tw0bpwxg_logs.txt _wazuh_dashboard.1.jhsqzw2biyzo0ddk7hyznzkek_logs.txt