<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40" xmlns:ns5="http://schemas.microsoft.com/office/2004/12/omml"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>  <style>  </style>  </head> <body lang=IT link=blue vlink=purple> <div class=Section1> I suppose this must be written into the plugin…. I don’t use check_by_ssh, so I didn’t know it didn’t have the –u option.<o:p></o:p> For example I have it in check_nrpe.<o:p></o:p> Another workaround could be to elevate the –t option. Try to set It to 60 secs, for example.<o:p></o:p> In your example you have two plugins, they both have a –t option. What if you try to elevate one or another until you don’t get timeout errors anymore?<o:p></o:p> By the way, do check_logfiles plugin have a –u option? If so, you could set –u, and a “–t” lower than the check_by_ssh one, so that the first plugin to go timed out should be the one with –u option… <o:p></o:p> <o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> Valerio Fabrizio * Technical Specialist * SunGard Global Trading * Via Degli Amedei, 15 20123 Milano, Italy Tel:+39 02 45442332 * Fax:+39 45 44 22 99 * Mobile:+39 3463949080 * valerio.fabrizio@sungard.com * www.sungard.com/globaltrading<o:p></o:p> </div> <o:p> </o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center tabindex=-1> </div> Da: Mirza Dedic [mailto:mirde@oppy.com] Inviato: giovedì 27 maggio 2010 16.12 A: 'nagiosplug-help@lists.sourceforge.net' Oggetto: Re: [Nagiosplug-help] R: check_by_ssh timed out issue<o:p></o:p> </div> <o:p> </o:p> How did you get the –u switch to appear on check_by_ssh?<o:p></o:p> <o:p> </o:p> Mine does not seem to have this, this is the output of –h for my plugin.<o:p></o:p> <o:p> </o:p> check_by_ssh v2002 (nagios-plugins 1.4.13)<o:p></o:p> Copyright (c) 1999 Karl DeBisschop <kdebisschop@users.sourceforge.net><o:p></o:p> Copyright (c) 2000-2008 Nagios Plugin Development Team<o:p></o:p> <nagiosplug-devel@lists.sourceforge.net><o:p></o:p> <o:p> </o:p> This plugin uses SSH to execute commands on a remote host<o:p></o:p> <o:p> </o:p> Usage: check_by_ssh -H <host> -C <command> [-fqv] [-1|-2] [-4|-6]<o:p></o:p> [-S [lines]] [-E [lines]] [-t timeout] [-i identity]<o:p></o:p> [-l user] [-n name] [-s servicelist] [-O outputfile]<o:p></o:p> [-p port] [-o ssh-option]<o:p></o:p> <o:p> </o:p> Options:<o:p></o:p> -h, --help<o:p></o:p> Print detailed help screen<o:p></o:p> -V, --version<o:p></o:p> Print version information<o:p></o:p> --extra-opts=[section][@file]<o:p></o:p> Read additionnal options from ini file<o:p></o:p> -H, --hostname=ADDRESS<o:p></o:p> Host name, IP Address, or unix socket (must be an absolute path)<o:p></o:p> -p, --port=INTEGER<o:p></o:p> Port number (default: none)<o:p></o:p> -4, --use-ipv4<o:p></o:p> Use IPv4 connection<o:p></o:p> -6, --use-ipv6<o:p></o:p> Use IPv6 connection<o:p></o:p> -1, --proto1<o:p></o:p> tell ssh to use Protocol 1 [optional]<o:p></o:p> -2, --proto2<o:p></o:p> tell ssh to use Protocol 2 [optional]<o:p></o:p> -S, --skip-stdout[=n]<o:p></o:p> Ignore all or (if specified) first n lines on STDOUT [optional]<o:p></o:p> -E, --skip-stderr[=n]<o:p></o:p> Ignore all or (if specified) first n lines on STDERR [optional]<o:p></o:p> -f<o:p></o:p> tells ssh to fork rather than create a tty [optional]. This will always return OK if ssh is executed<o:p></o:p> -C, --command='COMMAND STRING'<o:p></o:p> command to execute on the remote machine<o:p></o:p> -l, --logname=USERNAME<o:p></o:p> SSH user name on remote host [optional]<o:p></o:p> -i, --identity=KEYFILE<o:p></o:p> identity of an authorized key [optional]<o:p></o:p> -O, --output=FILE<o:p></o:p> external command file for nagios [optional]<o:p></o:p> -s, --services=LIST<o:p></o:p> list of nagios service names, separated by ':' [optional]<o:p></o:p> -n, --name=NAME<o:p></o:p> short name of host in nagios configuration [optional]<o:p></o:p> -o, --ssh-option=OPTION<o:p></o:p> Call ssh with '-o OPTION' (may be used multiple times) [optional]<o:p></o:p> -q, --quiet<o:p></o:p> Tell ssh to suppress warning and diagnostic messages [optional]<o:p></o:p> -w, --warning=DOUBLE<o:p></o:p> Response time to result in warning status (seconds)<o:p></o:p> -c, --critical=DOUBLE<o:p></o:p> Response time to result in critical status (seconds)<o:p></o:p> -t, --timeout=INTEGER<o:p></o:p> Seconds before connection times out (default: 10)<o:p></o:p> -v, --verbose<o:p></o:p> Show details for command-line debugging (Nagios may truncate output)<o:p></o:p> <o:p> </o:p> The most common mode of use is to refer to a local identity file with<o:p></o:p> the '-i' option. In this mode, the identity pair should have a null<o:p></o:p> passphrase and the public key should be listed in the authorized_keys<o:p></o:p> file of the remote host. Usually the key will be restricted to running<o:p></o:p> only one command on the remote server. If the remote SSH server tracks<o:p></o:p> invocation arguments, the one remote program may be an agent that can<o:p></o:p> execute additional commands as proxy<o:p></o:p> <o:p> </o:p> To use passive mode, provide multiple '-C' options, and provide<o:p></o:p> all of -O, -s, and -n options (servicelist order must match '-C'options)<o:p></o:p> <o:p> </o:p> Examples:<o:p></o:p> $ check_by_ssh -H localhost -n lh -s c1:c2:c3 -C uptime -C uptime -C uptime -O /tmp/foo<o:p></o:p> $ cat /tmp/foo<o:p></o:p> [1080933700] PROCESS_SERVICE_CHECK_RESULT;flint;c1;0; up 2 days<o:p></o:p> [1080933700] PROCESS_SERVICE_CHECK_RESULT;flint;c2;0; up 2 days<o:p></o:p> [1080933700] PROCESS_SERVICE_CHECK_RESULT;flint;c3;0; up 2 days<o:p></o:p> <o:p> </o:p> Notes:<o:p></o:p> See: http://nagiosplugins.org/extra-opts for --extra-opts usage and examples.<o:p></o:p> <o:p> </o:p> Send email to nagios-users@lists.sourceforge.net if you have questions<o:p></o:p> regarding use of this software. To submit patches or suggest improvements,<o:p></o:p> send email to nagiosplug-devel@lists.sourceforge.net<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Valerio.FABRIZIO@sungard.com [mailto:Valerio.FABRIZIO@sungard.com] Sent: May/26/2010 10:54 PM To: nagiosplug-help@lists.sourceforge.net Subject: [Nagiosplug-help] R: check_by_ssh timed out issue<o:p></o:p> </div> </div> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Hi<o:p></o:p> I’ve had the same problem with some remote checks, I solved it by adding a “-u” in the command. (“u” turns a time out critical into a time out unknown message). This works only if your plugin accept this value. <o:p></o:p> <o:p> </o:p> <o:p> </o:p> Regards <o:p></o:p> Valerio<o:p></o:p> <div> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center> </div> Da: Mirza Dedic [mailto:mirde@oppy.com] Inviato: giovedì 27 maggio 2010 5.18 A: <st1:PersonName w:st="on">'Nagios Plugin Help List'</st1:PersonName> Oggetto: Re: [Nagiosplug-help] check_by_ssh timed out issue<o:p></o:p> </div> <o:p> </o:p> I get that, but with the check script the “timed out” warning comes back as a critical.<o:p></o:p> <o:p> </o:p> I might be stuck with this as there is no “switch” to add to check_by_ssh for timed out values to not raise a critical condition as I’ve seen in some other scripts.<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Tony Parsonage [mailto:TParsonage@thiess.com.au] Sent: May/26/2010 5:02 PM To: Nagios Plugin Help List Subject: Re: [Nagiosplug-help] check_by_ssh timed out issue<o:p></o:p> </div> </div> <o:p> </o:p> You should be able to set the alert so that if you get an ‘unknown’ response then will not alert. I am unsure where this is set on the command line, my copy of Groundworks uses a web browser front end and it is set as below:<o:p></o:p> <o:p> </o:p> <img width=393 height=141 id="Picture_x005f_x005f_x005f_x0020_1" src="cid:image001.jpg@01CAFDBA.6A009D50"><o:p></o:p> <o:p> </o:p> If I untick the box for ‘unknown’ then save your configuration then I only get emails for Warning and Critical alerts.<o:p></o:p> <o:p> </o:p> <div> Tony <o:p></o:p> </div> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'> From: Mirza Dedic [mailto:mirde@oppy.com] Sent: Thursday, 27 May 2010 9:50 AM To: 'nagiosplug-help@lists.sourceforge.net' Subject: [Nagiosplug-help] check_by_ssh timed out issue<o:p></o:p> </div> </div> <o:p> </o:p> Hi List,<o:p></o:p> <o:p> </o:p> I have Nagios currently using check_by_ssh (check_by_ssh v2002 (nagios-plugins 1.4.13)) to check some of my remote servers, it calls a log script on the remote server and the log script returns a warning if the log files matches the criteria.<o:p></o:p> <o:p> </o:p> Every now and then, the check_by_ssh script gets timed out, and returns the message below.<o:p></o:p> <o:p> </o:p> Is there a way to suppress this at the Nagios box, so that Plugin Timed Out messages do not get emailed as “Critical”?<o:p></o:p> <o:p> </o:p> Anyone know? Below is my command definition..<o:p></o:p> <o:p> </o:p> define command{<o:p></o:p> command_name van-oppy-pro_data450<o:p></o:p> command_line $USER1$/check_by_ssh -H someserver -p 22 -i /home/nagios/.ssh/id_dsa -t 10 -C "/home/nagios/plugins/check_logfiles -t 30 -f /home/nagios/log_conf/usr1_data450.lg"<o:p></o:p> }<o:p></o:p> <o:p> </o:p> Nagios alert returned when the box being queried is very busy (this does not happen often, but creates a unwanted false positive warning):<o:p></o:p> <o:p> </o:p> CRITICAL - Plugin timed out while executing system call<o:p></o:p> <o:p> </o:p> <o:p> </o:p> Click <a href="https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==">here</a> to report this email as spam.<o:p></o:p> <pre>The Oppenheimer Group ---- CONFIDENTIAL<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.<o:p></o:p></pre><pre><o:p> </o:p></pre> <o:p> </o:p> _____________________________________________________________________<o:p></o:p> IMPORTANT - This email and any attachments may be confidential and privileged. <o:p></o:p> If received in error, please contact Thiess and delete all copies. You may not <o:p></o:p> rely on advice and documents received by email unless confirmed by a signed Thiess<o:p></o:p> letter. This restriction on reliance will not apply to the extent that the above email <o:p></o:p> communication is between parties to a contract and is authorised under that contract.<o:p></o:p> Before opening or using attachments, check them for viruses and defects. Thiess' <o:p></o:p> liability is limited to resupplying any affected attachments.<o:p></o:p> <o:p></o:p> <pre>The Oppenheimer Group ---- CONFIDENTIAL<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.<o:p></o:p></pre></div> </body> </html> <pre>The Oppenheimer Group ---- CONFIDENTIAL This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.