Solved Wazuh - Agents.Error. globalAgent is null
-
I am seeing the error, "Agents.Error. globalAgent is null", in a banner at the top of the page when I login to Kibana/Wazuh. It has been happening since I installed it (about 2 weeks ago). I only have 4 agents/systems while I play with it.
I can't seem to find much on it when Googling it. Does anyone know what it is/how to resolve?
-
I updated the server with all outstanding updates and there was a small update for Wazuh server and client side. I deployed the new client version and I didn't see that error after reconnecting. I will try it out tomorrow. It could be a fluke or something that was resolved in the update.
-
I didn't get the error when looking at the list of agents today. Looks like the update or reboot of the Wazuh server fixed it.
-
@wrx7m said in Wazuh - Agents.Error. globalAgent is null:
I didn't get the error when looking at the list of agents today. Looks like the update or reboot of the Wazuh server fixed it.
I know this is a necropost, but it's good to mention that mismatched version of manager and agent will almost always cause issues. It is recommended to comment out the repository until you are ready to update agents and manager at the same time.
-
@IRJ said in Wazuh - Agents.Error. globalAgent is null:
@wrx7m said in Wazuh - Agents.Error. globalAgent is null:
I didn't get the error when looking at the list of agents today. Looks like the update or reboot of the Wazuh server fixed it.
I know this is a necropost, but it's good to mention that mismatched version of manager and agent will almost always cause issues. It is recommended to comment out the repository until you are ready to update agents and manager at the same time.
That is interesting. I have been upgrading some of the agents on Linux systems when they are released, and later, upgrading the server side (I comment out/disable the repos for the server side, per their docs).
