New answers tagged

0

If you're using the EPEL packages, most of the plugins are split into separate packages so the check_snmp plugin is in the nagios-plugins-snmp package.


0

I just ran into this problem myself. The way I fixed it was to remove all of the whitespace from the allowed_hosts line. This is on nrpe 2.12 that's shipping on ubuntu 12.04. There is some documentation that indicated you should use ', ' for the field delimiter, however that does not appear to be the case.


0

Now that it's in there, you will need to run: /etc/init.d/nagios-nrpe-server restart Then it should be working. I would make this comment but I am not yet allowed.


2

First of all please note that *_period changes are not the same than a "scheduled downtime" in Nagios. Your problem is that you set a *_period only on the host, but not on the services. So your host check won't run and notify at the excluded times, but all the services will still run with the timeperiod from default.


1

Change check_nrpe!check_users!15!20 to check_nrpe!check_users!"15 20". With your current config, as far as Nagios is concerned: ARG1 = check_users ARG2 = 15 ARG3 = 20 But then your command only uses ARG1 and ARG2, so the 20 isn't passed to NRPE. You want ARG2 to be "15 20", which NRPE will then split into two ARGs on the receiving side.


0

You will have to write a custom plugin that keeps track of state in between invocations. This is not the usual model for Nagios plugins, which are typically run as independent, one-off, stateless programs. I'm not sure I entirely understand what you're trying to achieve, but one solution could be to store the check result along with a timestamp whenever you ...


0

You can try passing the actual values as thresholds in nrpe.cfg/nrpe.conf on remote host in place of $ARG1$ and $ARG2$. Eg : command[check_users]=/usr/lib64/nagios/plugins/check_users -w 15 -c 20 Along with this just to be sure, do check if : Check_Users command defined properly in commands.cfg on monitoring host. check if path of plugin(check_users) ...


0

collectd? their default interval is 10s. https://collectd.org/


2

I have found the solution ! Go to your template.cfg file and change in the contact part : FROM : service_notification_options w,u,c,r,f,s ; send notifications for all service states, flapping events, and scheduled downtime events host_notification_options d,u,r,f,s ; send notifications for all host states, flapping events, and scheduled ...


0

I was able to find the issue. The problem was with the check_mailq plugin. So after digging a bit and looking at it I was able to fix it. The fix was adding the sudo command withing the script. BEFORE elsif ( $mailq eq "exim" ) { ## open mailq if ( defined $utils::PATH_TO_MAILQ && -x $utils::PATH_TO_MAILQ ) { if (! ...


0

Enable debug in nrpe agent From:https://assets.nagios.com/downloads/nagioscore/docs/nrpe/NRPE.pdf How to go about debugging other problems... When debugging problems it may be useful to edit the NRPE configuration file and change the debug=0 entry to debug=1. Once you do that, restart the NRPE daemon if it is running as a standalone daemon. After you try ...


0

the NFS example will be tricky because there's no way for cross-host service dependencies automatically managed. You'll need a workaround there. You can monitor the exporting and nfs services properly (there's an nfsexports check, and you can also try checking rpcinfo connects) It'll leave a gap if i.e. a firewall fails, but if you monitor nfs well, focus on ...


0

To fix this issue without making the nagios plugin world-readable and/or world-executable, add the nrpe user to the nagios group.


0

I had the same symptom. So maybe this will save someone else some time. My problem was that I was missing the .cfg extension on the files in the include directory. My include dir was include_dir=/etc/nagios/nrpe.d The machine is running Ubuntu 14.04 for reference, using NRPE v2.15



Top 50 recent answers are included