NRPE : pb with a remote PERL script

[Tony]

I use nrpe to run a number of different checks using binary, perl and
bash script and nrpe has never complained about it.

It must be the output your script is giving that Nagios can't make any
sense of.

What does it check?
Can you run it from command line and get any output, what output does it
give?

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of marc.brun (Marc BRUN)
> Sent: 25 February 2003 10:03
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] NRPE : pb with a remote PERL script
> 
> Hello,
> 
> I try use a PERL script on remote host. But got : UNKNOWN ERROR,
unable to
> read output
> in Nagios...
> 
> Nagios is running ok.
> My perl script (check_mb) is running ok on local host. Nagios use it
correctly.
> My perl script is running ok when I am logged on the remote host and
run : perl
> check_mb
> My nrpe module is running ok when I try remote executable (check_disk
for
> instance)
> 
> Is there any incompatibily for nrpe module to run perl script instead
of executables
> ?
> 
> Thanx a lot,
> Marc
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> 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



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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