OK from command line, but not through the GUI, (incorrect co

Nagios Nagios Plugins support
1

Hello Nagios experts

Am new to Nagios, and need some help please:-

Installed Nagios 3.02, plugins 1.4.13 and have setup nrpe 2.12 on ubuntu 8.04

Run the following command from the Nagios host:-

/usr/local/nagios/libexec/check_nrpe -H adotntlx01 -c check_root

This brings back the following information:-

DISK OK - free space: / 67261 MB (97% inode=98%);| /=1554MB;57974;65221;0;72468

If I run the command (locally):-

/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /

I get:-

DISK OK - free space: / 67261 MB (97% inode=98%);| /=1554MB;57974;65221;0;72468

All OK so far.

However when I try this through the Nagios client…

Have set up a new command file called adotntlx01.cfg

Have the following entry:-

define service{
use generic-service ; Name of service template to use
host_name adotntlx01
service_description Check Root
check_command check_nrpe!check_root
}

nrpe.conf entry on remote host:-

command[check_root]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /

And get the following error in through the web gui:-

Check Root UNKNOWN 10-15-2008 12:30:46 0d 0h 0m 52s 2/3 Incorrect command line arguments supplied

How can the command line arguments be wrong if they work from the command line itself?

Can someone tell me where I am going wrong please?

Thanks
Olle

2

Hm, don’t have a right answer. Try to downgrade to lower version nad check if it works ok, like the user that wrote lower post:
meulie.net/portal_plugins/fo … c.php?7539

3

Thanks for that, I could go back to 1.4.12 or 1.4.11, or maybe even 0.22, which I may try, however if there is a bug and not a user configuration problem maybe this should be reported accordingly?

Thanks
Olle

4

Anyone who has anymore nuggets of wisdom could they please say now as I will be ‘starting again’ tomorrow. Letting me know of a latter version of nagios/plugins/nrpe that definately works would be a good start.

Thanks
Olle

5

Apologies for not writing sooner, however this has been resolved, I used Centos 5.2 with the latest installs.

Thanks
Olle