Support for Nagios products and services
https://support.nagios.com/forum/
-bheden wrote:After reviewing the configuration files you posted, a few things stick out:
You do not have all of your hostgroups listed in the NEB config in the worker configs. Some are missing.
Those will be orphaned.
You have some hostgroups specified in both the hostgroups directive and the localhostgroups. I've actually never seen someone do that, but I assume it could end up orphaned as well.
Remember that whatever hostgroup and servicegroup you define to split into a queue in the NEB config HAS TO HAVE A CORRESPONDING DEFINITION on one of the workers. (Or it will be orphaned).
Hi @bheden - Thanks for your answer.bheden wrote:Let's redefine the problem for clarity:
Some hostchecks are being sent to a gearman worker where they are failing.
This begs the question ..do all of the gearman workers have the proper routes to all of the hosts?
If not, maybe just having a generic catchall hosts=yes isn't going to work for you. You may have to specify all of your hosts into a hostgroup so that they can all end up on a gearman worker that has the necessary routes.
Your first step is going to be logging in to each of the 6 gearman workers and manually running the host check command in its entirety. It will likely be something like this:All of the gearman workers that have the directive 'hosts=yes' have the necessary routes to the hosts.
Code: Select all
/usr/local/nagios/libexec/check_icmp -H 127.0.0.1 -w 3000.0,80% -c 5000.0,100% -p 5bheden wrote:Your first step is going to be logging in to each of the 6 gearman workers and manually running the host check command in its entirety. It will likely be something like this:All of the gearman workers that have the directive 'hosts=yes' have the necessary routes to the hosts.
You'll have to login as the user the gearman_worker service is running as (Likely user 'nagios' but could be something else depending on where you installed the packages from).Code: Select all
/usr/local/nagios/libexec/check_icmp -H 127.0.0.1 -w 3000.0,80% -c 5000.0,100% -p 5
I don't believe it's permission, but possibly routing. When you ran the check - did you run check_icmp against 127.0.0.1 or did you specify the IP of a check that is failing? If it's routing related, 10.0.0.0/8 may not have a route to 192.168.5.0/24. One of the workers may not be able to reach 192.168.5.0/24 which would explain the issue.maartin.pii wrote:bheden wrote:Your first step is going to be logging in to each of the 6 gearman workers and manually running the host check command in its entirety. It will likely be something like this:All of the gearman workers that have the directive 'hosts=yes' have the necessary routes to the hosts.
You'll have to login as the user the gearman_worker service is running as (Likely user 'nagios' but could be something else depending on where you installed the packages from).Code: Select all
/usr/local/nagios/libexec/check_icmp -H 127.0.0.1 -w 3000.0,80% -c 5000.0,100% -p 5
Hi @bheden - I've alredy done what you asked to me and the execution of the command was successful on each worker as the 'nagios' user.
I don't think that this could be a permissions issue.
I've tried both. I have all my firewalls routes ok. And it has sense because none of my service checks has errors. And what is more, if it would be a routing issue the error should be something like 'host unreachable' or 'host down' but not 'orphan check (is host queue running)' - wouldn't it?bheden wrote:
I don't believe it's permission, but possibly routing. When you ran the check - did you run check_icmp against 127.0.0.1 or did you specify the IP of a check that is failing? If it's routing related, 10.0.0.0/8 may not have a route to 192.168.5.0/24. One of the workers may not be able to reach 192.168.5.0/24 which would explain the issue.