Nagios 2.3.1, problems with perl plugins

[Frederik Vanhee]

Stanley.Hopcroft at Dest.gov.au wrote:

>Dear Folks,
>
>I am writing to thank you for your letters and say,
>
>  
>
>>-----Original Message-----
>>    
>>
>
>  
>
>>Message: 17
>>From: Michael =?iso-8859-1?q?H=FCttig?= 
>>   <Michael.Huettig at medien-systempartner.de>
>>Organization: MSP
>>To: nagios-users at lists.sourceforge.net
>>Subject: Re: [Nagios-users] RE: Nagios 2.3.1, problems with 
>>perl plugins
>>Date: Wed, 17 May 2006 15:40:22 +0200
>>Cc: Stanley.Hopcroft at dest.gov.au
>>
>>Hi Stanley,
>>i=B4ve posted on monday the following message. I think there 
>>was a problem =  with=20 embedded perl. Which perl-plugins do you use?
>>
>>I just upgraded my Nagios-2.0 to nagios-2.3. Both Versions 
>>were compiled wi= th=20 epn-support with 
>>--enable-embedded-perl --with-perlcache
>>
>>Runnning nagios-2.0 all checks using perl-plugins 
>>(check_smart,=20 check_cisco_env, check_ifoperstatus and 
>>others) were doing fine.
>>
>>Using nagios-2.3 i got the following errors:
>>check_ciscoenv.pl
>>;Cisco environmental health;UNKNOWN;HARD;3;UNKNOWN: Unable to 
>>resolve=20 destination address '-c'
>>
>>check_load.pl
>>;Load;UNKNOWN;SOFT;2;**ePN 
>>/usr/local/nagios/libexec/check_load.pl: "Argume= nt=20 "" 
>>isn't numeric in numeric lt (<) at (eval 12) line 61,".
>>
>>check_ifoperstatus.pl
>>;UNKNOWN;notify-by-email;**ePN 
>>/usr/local/nagios/libexec/check_ifoperstatus=
>>:=20
>>Option d requires an argument.
>>
>>check_smart.pl
>>;S.M.A.R.T-Status;UNKNOWN;SOFT;1;**ePN 
>>/usr/local/nagios/libexec/check_smar=
>>t.pl:=20
>>"Can't exec "sudo": No such file or directory at (eval 15) line 119,".
>>
>>check_traffic.pl
>>;Traffic ISDN-Interface;CRITICAL;notify-by-email;CRITICAL: 
>>Could not match=  ISDN Basic Rate Interface (S0)
>>
>>    
>>
>
>Firstly thanks to Frederick and Michael for the notification about this
>serious problem.
>
>Unfortunately the situation as I see it is,
>
>1 I am running 2.3 not 2.3.1 and so my limited Perl plugins (home-brew)
>may not be picking up the problem. Also I lack a Nagios work bench at
>the
>moment so its going to be slow if heavy lifting is involved as it seems.
>
>2 A quick glance at the CVS does not seem to show any relevant changes
>
>2.1 there appear to be no changes in checks.c near the embedded Perl
>code
>2.2 the change to p1.pl was only to allow plugins to return more than
>one
>line of output (the nagios-snmp plugins do this I think).
>
>3 If Michael or Frederick would enable the LOGGING options in the copy
>of p1.pl they use for new_mini_epn (perldoc p1.pl should help).
>
>IIRC you want to change this p1.pl to have
>
>use constant  DEBUG_LEVEL             => LEAVE_MSG ;
>
>and make sure the plugin log path looks Ok.
>
>This will leave messages like
>
>Mon Mar  6 15:43:39 2006 run_package:
>"/usr/lib/nagios/plugins/check_rootport -H 10.0.254.167 -N BRUSW200"
>returning (0, "Ok. No topology change: root port of
>10.0.254.167/BRUSW200 has not changed from that expected: 513. See <a
>href="http://nms/cgi-bin/display_spanning_tree">Current spanning tree
>graph</a>.
>").
>Mon Mar  6 15:43:39 2006 eval_file:
>/usr/lib/nagios/plugins/check_rootport already successfully compiled and
>file has not changed; skipping compilation.
>Mon Mar  6 15:43:39 2006 run_package:
>"/usr/lib/nagios/plugins/check_rootport -H 10.0.254.170 -N MTASW200"
>returning (0, "Ok. No topology change: root port of
>10.0.254.170/MTASW200 has not changed from that expected: 0. See <a
>href="http://nms/cgi-bin/display_spanning_tree">Current spanning tree
>graph</a>.
>").
>Mon Mar  6 15:43:39 2006 run_package:
>"/usr/lib/nagios/plugins/check_rootport -H 10.0.254.168 -N MTASW207"
>returning (0, "Ok. No topology change: root port of
>10.0.254.168/MTASW207 has not changed from that expected: 1. See <a
>href="http://nms/cgi-bin/display_spanning_tree">Current spanning tree
>graph</a>.
>").
>
>in the log file (also named in p1.pl).
>
>This should provide some clues.
>
>The only quick workaround that may be worth a _try_ is to replace pl.pl
>for an older one from CVS (say 1.7).
>However, I am not confident.
>
>Perhaps my installation is a bit atypical: every one of the 2.0 series
>(inc betas) has 
>been in prod use with either heavy or light embedded Perl without a
>hitch.
>
>The last random thought is, could you have changed Perl or
>Text::ParseWords around about the
>time the problem started ? This module is responsible for argument
>processing and this
>appears to be breaking. OTOH, if it was the culprit, all versions would
>be b0rked.
>
>Good luck,
>
>Yours sincerely.
>
>
>-------------------------------------------------------
>Using Tomcat but need to do more? Need to support web services, security?
>Get stuff done quickly with pre-integrated technology to make your job easier
>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
>_______________________________________________
>Nagios-users mailing list
>Nagios-users at lists.sourceforge.net
>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
>
>  
>
Thanks for the hints Stanley,

as soon as I can, I will do some testing although this is not easy 
because I'm running a production system, I will try to set up a system 
for testing.
I didn't change the Text::Parsewords, so the only thing I can do is to 
enable the logging.

Frederik


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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