Nagios start error about ansible-nagios

[sadsfae]

Hey @adsizzler can you post the contents of your hosts inventory file please? More than likely you've got a host entered under more than one category, they should not belong to more than one type of check category the way that the playbook operates and is templated.

e.g.

[servers]
host-01

[webservers]
host-02

It's ok though, they all have similar checks depending on type. For example the webservers group inherits all the normal servers checks plus HTTP.

[ranjeetranjan]

It solved now. Thanks for your response. But now i am getting 2 error

1. 255 is out of bounds
2. DISK CRITICAL - /dev/root is not accessible: No such file or directory

[sadsfae]

Ansible uses the following to determine your root disk name, and this is the first time I've seen it not choose the correct one.

e.g.

https://github.com/sadsfae/ansible-nagios/blob/master/install/roles/nagios-client/templates/nrpe.cfg.j2#L205

{{ ansible_mounts[0]['device'] }}

What does your df -h output look like on your host? What about ls /dev/mapper/* ?
Do you have python installed on the target system that is giving the error?

What does your /etc/nagios/nrpe.cfg have in it for what's generated in the check_root?

cat /etc/nagios/nrpe.cfg | grep check_root

255 is out of bounds may be indicative of selinux blocking nagios plugin checks (this is common unfortunately), also try setting setenforce 0 and seeing if that makes it go away when you re-run the playbook.

Also check if there is anything in /var/log/audit/audit.log

cat /var/log/audit/audit.log | grep -i avc | audit2why