Hi all,
we have noticed something weird regarding active checks. Version of server and agent are both 1.8.2.
We have defined a couple of active checks for the agent. When the agent starts, it issues a refresh_active_checks to the server. The server sometimes responds with an empty set of active checks, and sometimes with the full list of checks that are defined for the agent.
This behaviour is not really reproducible, at least we've found no way to reliable reproduce it. However, when we disable the active checks via the GUI, re-enable them and then start the agent, the server will happily send the list of active checks the first time asked. The next results are again empty sets. When we start the agent without the above procedure, the agent initially gets an empty set and it takes quite a while until the agent gets the set of active checks and performs them.
Might this be a caching issue? If yes, is there a switch to modify this behaviour?
Any pointers are appreciated!
we have noticed something weird regarding active checks. Version of server and agent are both 1.8.2.
We have defined a couple of active checks for the agent. When the agent starts, it issues a refresh_active_checks to the server. The server sometimes responds with an empty set of active checks, and sometimes with the full list of checks that are defined for the agent.
This behaviour is not really reproducible, at least we've found no way to reliable reproduce it. However, when we disable the active checks via the GUI, re-enable them and then start the agent, the server will happily send the list of active checks the first time asked. The next results are again empty sets. When we start the agent without the above procedure, the agent initially gets an empty set and it takes quite a while until the agent gets the set of active checks and performs them.
Might this be a caching issue? If yes, is there a switch to modify this behaviour?
Any pointers are appreciated!