Nagios reporting localhost statistics instead of remote machine

nagios

I'm a little baffled by this – I set up Nagios3's server process on one machine (tala) and NPRE on two others (medea and iiyanara.), and thought it was set up correctly. For various frustrating reasons I had to rebuild medea from a disk image, and as a result NPRE isn't installed anymore.

Imagine my surprise when Nagios is (days later) continuing to merrily report not only that my server is up, but also a series of performance metrics like total processes, etc. As it turns out, I'm pretty sure the Nagios instance has actually been reporting on localhost for both medea and iiyanara all along.

Here's the initial block + first service block from medea.conf:

define host{
    use                     generic-host            ; Name of host template to use
    host_name               medea.phyre.im
    alias                   Medea
    address                 97.107.128.112
    }

define service{
    use                             generic-service         ; Name of service template to use
    host_name                       medea.phyre.im
    service_description             Disk Space
    check_command                   check_all_disks!20%!10%
}

Curiously, if I specify a different IP, Nagios reports that the machine is down. So either:

  1. Nagios is using black sorcery to commune with medea despite a total absence of the NPRE service
  2. Nagios is reporting on localhost for some reason

…And then it STOPS doing those things if I specify, for instance, 197.107.128.112 as the target IP.

My question is basically this: what the hell?

Best Answer

check_all_disks probably uses check_disk plugin which check amount of used space of locally mounted filesystems.

You should use something like: 

check_nrpe!check_all_disks
Related Topic