Perl plugins: No output from plugin

[Dennis Hopp]

Well I recompiled without the embedded perl interpreter and everything
seems to be working now.  

I've seen the SPEC files of the rpm packages and they configure with
--embedded-perl and --perl-cache ...must be something I did wrong...

Oh well for now, I don't have enough hosts/services to worry about the
overhead.

Thanks for everybody's help!

--Dennis

> -----Original Message-----
> From: Chester R. Hosey [mailto:Chester.Hosey at gianteagle.com]
> Sent: Tuesday, August 23, 2005 10:33 AM
> To: Dennis Hopp
> Cc: Subhendu Ghosh; nagios-users at lists.sourceforge.net
> Subject: RE: [Nagios-users] Perl plugins: No output from plugin
> 
> On Tue, 2005-08-23 at 10:29 -0500, Dennis Hopp wrote:
> > I don't get a file in /tmp...
> >
> >
> > # 'check_linux_load' command definition
> > define command{
> >         command_name    check_linux_load
> >         command_line    $USER1$/check_snmp_load.pl -H $HOSTADDRESS$
-C
> > public -w $ARG1$ -c $ARG2$ -L > /tmp/plugin_output.tmp |echo $?
> >
> > #       command_line    $USER1$/check_snmp_load.pl -h
> > }
> >
> > --Dennis
> 
> Try using the 'tee' command in your definition -- even if the command
> generates no output, tee will at least create a 0-length file.
> 
> command_line    $USER1$/check_snmp_load.pl -H $HOSTADDRESS$ -C public
-w
> $ARG1$ -c $ARG2$ -L | /usr/bin/tee /tmp/plugin_output.tmp
> 
> (Verify path to 'tee', of course.)
> 
> Chet


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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