This is a service check command. I'd like to somehow get the current notification count into my check script.
Cheers, Jeff Orr Attributor Corporation ----- Original Message ----- From: "Patrick Morris" <[EMAIL PROTECTED]> To: "Jeff Orr" <[EMAIL PROTECTED]> Cc: "nagios-users" <[email protected]> Sent: Tuesday, August 21, 2007 2:46:49 PM (GMT-0800) America/Los_Angeles Subject: Re: [Nagios-users] Missing $NOTIFICATIONUMBER$ macro Hi Jeff! On Tue, 21 Aug 2007, Jeff Orr wrote: > I have an odd problem with Nagios 2.9 and NRPE 2.8x. I'm wrapping check_nrpe > in a script to detect socket timeouts; the script returns a WARNING instead > of an UNKNOWN for the first two socket timeouts, and a CRITICAL thereafter. > I'm using $NOTIFICATIONNUMBER$ to pass in the current notification count. > > The problem is that $NOTIFICATIONNUMBER$ does not seem to be being passed to > me script. Here is what I have in checkcommands.cfg, in which > $NOTIFICATIONNUMBER$ gives a null value in my PERL script: > > define command{ > command_name check__data_disk2 > command_line $USER1$/nrpe_wrapper -H $HOSTADDRESS$ -c check_disk3 -S > $SERVICESTATE$ -N $NOTIFICATIONNUMBER$ > } Is this used as a check or a notification command? There is no notification number associated with a service check; only with a notification. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
