Nagios Support Forum

Is it possible to specify a timeperiod so I only get notifications for a system off-hours? Can I specify the range like " monday 18:00-08:00 ", or do I have to do something like " monday 00:00-08:00,18:00-24:00 "? I have been asked to monitor certain QA systems after hours. I don...

And I fixed it. Under "configure service", "monitoring" tab, I changed the command string to this: check_nrpe!check_disk_all!5!10 removed the "-n" from /etc/sysconfig/nrpe on the remote host (added only because it was failing on SSL out of the gate), and restarted nrpe ...

Here's what I ended up running to get the strace: strace -o /root/nrpe_strace.log -ff /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -f -n Which produced these files: -rw-r--r-- 1 root root 588 Jun 18 13:57 nrpe_strace.log -rw-r--r-- 1 root root 223 Jun 18 15:28 nrpe_strace.log.60978 -rw-r--r-- 1 root root ...

ps -ef|grep nrpe|grep -v grep nrpe 87277 1 0 Jun17 ? 00:00:00 /usr/sbin/nrpe -c /etc/nagios/nrpe.cfg -f -n And the pid file has the correct PID in it, both /var/run/nrpe and /usr/lib64/nagios/plugins/ have execute permissions for "other" all the way down the tree so the nrpe user can navig...

Here's the uncommented content: [root@cliplsat01 ~]$ grep -v "^#" /etc/nagios/nrpe.cfg |grep . log_facility=daemon pid_file=/var/run/nrpe/nrpe.pid server_port=5666 nrpe_user=nrpe nrpe_group=nrpe allowed_hosts=127.0.0.1,xxx.xxx.xxx.xxx (Nagios host address) dont_blame_nrpe=1 allow_bash_comm...

No selinux, but good question, that's all too often in the way: [root@cliplsat01 ~]$ sestatus SELinux status: disabled disabled on the Nagios system as well: $ sestatus SELinux status: disabled firewalld was running on the Nagios system; I stopped it but that didn't make a difference, still getting ...

Are you seeing any errors in the syslog on the remote machine when trying to execute the above? Yes, I get this, from my initial post: Jun 17 10:12:29 cliplsat01 nrpe[20536]: WARNING: my_system() seteuid(0): Operation not permitted Which is inexplicable, as nothing that the plugin is doing should r...

this I know but you have the -c and -w defined in the nrpe command so they shouldn't be passed again Ah,thanks for that, I clearly missed it. Forest vs trees problem, and I'm target-fixated on specific trees. Pulling back.... This fails: $ su nrpe -c "/usr/lib64/nagios/plugins/check_mem.py -c ...

Changing the ownership on the plugin to be exclusively nrpe doesn't produce new results; it still runs on the host: ls -l /usr/lib64/nagios/plugins/check_mem.py -rwxr-xr-x 1 nrpe nrpe 2808 Jun 14 15:34 /usr/lib64/nagios/plugins/check_mem.py [root@cliplsat01 plugins]$ /usr/lib64/nagios/plugins/check_...

This still fails running on the Nagios system: $ /usr/local/nagios/libexec/check_nrpe -n -H cliplsat01 -c check_mem.py -a "10 5" NRPE: Unable to read output Also, the plugin will fail if both the 'w' and the 'c' are not explicitly included: $ /usr/lib64/nagios/plugins/check_mem.py 10 5 UNK...