Tag Info

New answers tagged

1

You need some type of configuration management software to setup and install nrpe daemon on each remote host as well as deploy the configurations and ultimately your plugins. May I suggest Ansible for this task. https://github.com/bobmaerten/ansible-role-nagios-nrpe-server


1

From check_load --help: -r, --percpu Divide the load averages by the number of CPUs (when possible) This isn't guaranteed to work on every OS... it uses sysconf to query the number of CPUs (_SC_NPROCESSORS_ONLN or _SC_NPROCESSORS_CONF). I seem to recall it not reporting the correct values on AIX. Not a problem on Linux though. The oldest version I ...


0

Add the specific host with a ! prefix in the service definition. The service check below will apply to all hosts in agroup apart from ahost. define service { hostgroup_name agroup host_name !ahost service_description Shared NFS mount check_command check_nrpe!check_shared_mount use generic-service }


0

you can edit check parameters in check_mk by creating a rule for the service. By creating a rule can overwrite the default values for a service. If you are using WATO you can get to the rule creation dialog by clicking on the third icon from the right in the service overview screen. The icon looks like this: In the following dialog you can either set "no ...


4

In NagiosXI, you can use the following command: /usr/local/nagiosxi/scripts/reset_nagiosadmin_password.php --password=<newpassword> If you're using an older version, you need to identify the location of the htpasswd.users file (usually /etc/nagios/) and run the following command: htpasswd -c -b /etc/nagios/htpasswd.users nagiosadmin ...


0

Small enhancement of pQd's answer: #!/bin/bash URL=$1 RESPONSE_CODE=${2:-200} TIMEOUT=${3:-10} case $RESPONSE_CODE in 401) EXPECTED_RETURN_CODE=6 ;; 200) EXPECTED_RETURN_CODE=0 ;; *) EXPECTED_RETURN_CODE=0 ;; esac start=`date +%s` wget -t 1 --timeout ${TIMEOUT} -O /dev/null -o /dev/null -e http_proxy=PUTYOURPROXYHERE:8080 ${URL} ...


1

If you are using 0.4.3 (which I assume) "default" security has been improved a bit. This unfortunately means the rather insecure check_nrpe wont work. When you install NSClient++ you have the option of selecting "insecure mode" which should work fine with the classic check_nrpe. You can also tweak this "in post" using the nrpe command like so: nscp nrpe ...


1

command_line /etc/nagios/commands/make-ticket-wrapper "$SERVICESTATE$" "$SERVICESTATETYPE$" "$HOSTNAME" "$HOSTADDRESS$ "$HOSTSTATE" "$HOSTGROUPALIAS" "$SERVICEDESC" You're missing a double quote after $HOSTADDRESS$, and missing a $ at the end of HOSTNAME, HOSTSTATE, HOSTGROUPALIAS, and SERVICEDESC. When you miss a double quote, it screws up the rest of ...


0

nagios chokes on all those quotes change: command_line /etc/nagios/commands/make-ticket-wrapper "$SERVICESTATE$" "$SERVICESTATETYPE$" "$HOSTNAME" "$HOSTADDRESS$ "$HOSTSTATE" "$HOSTGROUPALIAS" "$SERVICEDESC" to: command_line /etc/nagios/commands/make-ticket-wrapper $SERVICESTATE$ $SERVICESTATETYPE$ $HOSTNAME$ $HOSTADDRESS$ $HOSTSTATE$ ...


0

NSClient++ 0.4.3 has a built in check_pagefile which can be used to monitors page file utilization.


2

You need to send Cookie in header: Key Value Cookie wbisessionkey=ee7426964a6d14788ba86f77764733bf; wbiusername=monitoruser something like this (code not tested): cookie = "wbiusername={0}; wbisessionkey={1}".format(username,sessionid); req_system.add_header('Cookie', cookie);



Top 50 recent answers are included