I followed a previous post by mslansing (April 2012).
My client is on a SuSE 11 server. The check_nrpe is already in commands.cfg file, I didn't have to add it.
When I run /usr/local/nagios/libexec/check_nrpe -H <<remost host>> -c check_load -a '-w 15,10,5 -c 30,20,10', the error I get:
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
On my remote log:
Error: Request contained command arguments, but argument option is not enabled!
I'm not seeing any parameter for a temp location in nrpe.cfg file.
I changed the dont_blame_nrpe=0 line to a "1", then save the file and issued:
service xinetd restart
Still no change.
check_nrpe!check_load command failed
Re: check_nrpe!check_load command failed
It's 64 bit running on VMware 5.
Re: check_nrpe!check_load command failed
Some of the file locations are different on SuSE:
SuSE:
/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
/usr/lib/nagios/plugins/
CentOS:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load -a '-w 15,10,5 -c 30,20,10'
/usr/local/nagios/libexec
SuSE:
/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
/usr/lib/nagios/plugins/
CentOS:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load -a '-w 15,10,5 -c 30,20,10'
/usr/local/nagios/libexec
Re: check_nrpe!check_load command failed
What I'm finding is that the command:
Doesn't work:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load -a '-w 15,10,5 -c 30,20,10'
Does work:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load
My remote server doesn't like the attached arguments. I have even tried matching the remote's hardcoded command with the command run on the monitor server side.
Doesn't work:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load -a '-w 15,10,5 -c 30,20,10'
Does work:
/usr/local/nagios/libexec/check_nrpe -H REMOTEIP -c check_load
My remote server doesn't like the attached arguments. I have even tried matching the remote's hardcoded command with the command run on the monitor server side.
- Box293
- Too Basu
- Posts: 5126
- Joined: Sun Feb 07, 2010 10:55 pm
- Location: Deniliquin, Australia
- Contact:
Re: check_nrpe!check_load command failed
I think that you need to complile NRPE on the SuSE box with the --enable-command-args parameter:
I was playing around with NRPE on SuSE a few months ago and here are the notes I made:
I was playing around with NRPE on SuSE a few months ago and here are the notes I made:
Code: Select all
cd /var/tmp
sudo wget http://sourceforge.net/projects/nagios/files/nrpe-2.x/nrpe-2.15/nrpe-2.15.tar.gz
sudo tar zxvf nrpe-2.15.tar.gz
cd nrpe-2.15/
sudo ./configure --enable-command-args
sudo make all
sudo make install-plugin
sudo make install-daemon
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Re: check_nrpe!check_load command failed
Currently, the YAST download I have is NRPE v2.12. Will this work with this version or will I need to upgrade first.
It's very convenient to use YAST for this so I would like to keep this process, if possible.
It's very convenient to use YAST for this so I would like to keep this process, if possible.
Re: check_nrpe!check_load command failed
I don't know enough about Yast to know if there is a way to rebuild the agent within the pkg management system. Lets test whether it supports command args currently - run a check against the server with command arguments declared in the check, and then on teh remote server check messages:
You are looking for any errors dealing with command args.
Code: Select all
tail -40 /var/log/messagesFormer Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: check_nrpe!check_load command failed
I think I've figured out that it was an input mistake on the remote server for the commands. I've corrected that and now it works from the monitor server's command line.