[Nagiosplug-help] Problem with check_rpc ...

[Harper Mann]

When the check ran properly from the command line, was it run from the
"nagios" user id?  It could be a permissions or path problem.  Try "su -
nagios" and rerun "../path/check_rpc -H server_IP -C nfs -c2,3" using the
IP.

One other thought: double check that $USER1$ is properly defined and / or
try replacing it with the proper path in checkcommands.cfg.  

- Harper

Harper Mann
Groundwork Open Source Solutions
510-599-2075 (cell)


-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of Oliver
Kaltenecker
Sent: Tuesday, September 21, 2004 12:35 AM
To: nagiosplug-help at lists.sourceforge.net
Subject: [Nagiosplug-help] Problem with check_rpc ...

On 2003-11-15 04:23 Pedro Silveira Vieira da Silva had a problem with 
check_rpc. Now I am facing the same problem:

Interactively called "check_rpc -H server -C nfs -c2,3" works, but the 
same configured for automated check via nagios results in "No output!".

Here is my entry in checkcommands.cfg

# 'check_nfs' command definition
define command{
         command_name    check_nfs
         command_line    $USER1$/check_rpc -H $HOSTADDRESS$ -C nfs -c2,3
         }

Since there is no answer in the archives and I couldn't find any help in 
the documentation/FAQ I repost the problem to the list.

What am I doing wrong?

    Oliver.


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null