[Nagiosplug-help] Problems with check_rpc (nagios-plugins 1.3.1) 1.7

[Subhendu Ghosh]

We should look into that - probably LANG=C -- along with the changes for 
i18n

-sg

On Fri, 8 Aug 2003, Voon, Ton wrote:

> Subhendu,
> 
> That's a good point generally - should we set the locale before running all
> external commands?
> 
> Ton
> 
> > -----Original Message-----
> > From: Subhendu Ghosh [mailto:sghosh at sghosh.org] 
> > Sent: Friday, August 08, 2003 3:40 PM
> > To: ecejgv at eresmas.com
> > Cc: nagiosplug-help at lists.sourceforge.net
> > Subject: RE: Re: [Nagiosplug-help] Problems with check_rpc 
> > (nagios-plugins 1.3.1) 1.7
> > 
> > 
> > 
> > What locale setting are your running with?  It looks like 
> > rpcinfo has the 
> > correct output but may have other characters due to locale 
> > setting and 
> > that causes the parser to fail.
> > 
> > -sg
> > 
> > On Fri, 8 Aug 2003 ecejgv at eresmas.com wrote:
> > 
> > > 
> > > Hi:
> > > 
> > > I have executed the command with -v and the answer is:
> > > 
> > > [root at futurespace libexec]# ./check_rpc -H localhost -C nfs 
> > -p2049 -c2,3 -v
> > > Checking nfs version 2 proto u
> > > /usr/sbin/rpcinfo -n 2049 -u localhost 100003 2 2>&1 |
> > > the program 100003 version 2 is ready and waiting
> > >  Checking nfs version 3 proto u
> > > /usr/sbin/rpcinfo -n 2049 -u localhost 100003 3 2>&1 |
> > > the program 100003 version 3 is ready and waiting
> > >  UNKNOWN: RPC program nfs  udp is not running
> > > 
> > > I have also executed a debuger in perl (perl -d check_rpc 
> > -H localhost -C nfs -p2049 -c2,3. I enclose it in the
> > > file.
> > > 
> > >   The best regards and thanks in advance, Javier.
> > > 
> > >  
> > > 
> > > 
> > >  
> > > 
> > > 
> > > 
> > > ----- Mensaje Original -----
> > > Remitente: Subhendu Ghosh sghosh at sghosh.org
> > > Destinatario: ecejgv at eresmas.com
> > > Fecha: Viernes, Agosto 8, 2003 5:03am
> > > Asunto: Re: [Nagiosplug-help] Problems with check_rpc 
> > (nagios-plugins 1.3.1) 1.7
> > > 
> > > >
> > > >Can you run the program with the verbose option (-v)
> > > >
> > > >My results: (RH 7.2)
> > > >[sghosh at calcutta plugins-scripts]$  ./check_rpc -H localhost -C
> > > >nfs -p
> > > >2049 -c2,3
> > > >OK: RPC program nfs version 2 version 3 udp running
> > > >
> > > >-sg
> > > >
> > > >
> > > >On Thu, 7 Aug 2003 ecejgv at eresmas.com wrote:
> > > >
> > > >>
> > > >> Hi:
> > > >>
> > > >> I contact you because I have a problem with the script check_rpc
> > > >version 1.7 (nagios-plugins 1.3.1).
> > > >>
> > > >> I have a machine (futurespace) with Linux RedHat 8.0 and with a
> > > >NFS server started.
> > > >>
> > > >> (RPC program=nfs, port=2049, versions=2,3, protocol=udp).
> > > >>
> > > >> I want to check if the NFS server is running. For that I execute
> > > >a check_rpc -H futurespace -C nfs -p 2049 -c2,3
> > > >> but the answer is "UNKNOWN: RPC program nfs  udp is not running".
> > > >>
> > > >> Really the NFS server is running in my machine but the plugin
> > > >check_rpc doesn't find
> > > >>
> > > >> it. How can I solve this problem???
> > > >>
> > > >> Moreover I have tried the NIS server (RPC program = ypserv) but
> > > >it hasn't worked either. I get the same error
> > > >> message.
> > > >>
> > > >> I enclose a log with these testings.
> > > >>
> > > >> The best regards and thanks in advance for your 
> > attention, Javier.
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >--
> > > >
> > > >
> > > 
> > > 
> > > 
> > > 
> > 
> > -- 
> > 
> > 
> 
> 
> This private and confidential e-mail has been sent to you by Egg.
> The Egg group of companies includes Egg Banking plc
> (registered no. 2999842), Egg Financial Products Ltd (registered
> no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
> carries out investment business on behalf of Egg and is regulated
> by the Financial Services Authority.  
> Registered in England and Wales. Registered offices: 1 Waterhouse Square,
> 138-142 Holborn, London EC1N 2NA.
> If you are not the intended recipient of this e-mail and have
> received it in error, please notify the sender by replying with
> 'received in error' as the subject and then delete it from your
> mailbox.
> 

--