Additionally, Nagios is really sensitive about how the Perl script is written. It should be written well-enough to run with "use strict" without any errors. (I see that it is commented out of both of your scripts.) Additionally, the embedded Perl interpreter causes the scripts to be run in what I consider to be a somewhat "non-standard" way in regards to how the parameters are sent to the script. (In our installation we have to surround host and service macros with quotes before sending them to any plugins written in Perl.) The copyright date on that file is 2000, so you will definitely want to find (or write) a more up to date version.
On 08/16/2010 05:37 PM, Tony Yarusso wrote: > This probably means that a subroutine from one of the used perl > libraries is bailing out with an error, although why I don't know. Are > you sure you're passing all of the arguments the same on the command > line as Nagios is? One thing that I can tell you is that those plugins > are out of date, since they use the old value of -1 for Unknown which > should be 3 now, so who knows what other issues there are. (Sorry I > can't tell you more - I don't really do Perl.) > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Nagios-users mailing list Nagios-users@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