<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-15" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Dear all and Hari, Thanks for your help. I figured out the problem to be with resources.cfg. USER1 was defined as a location that did have the nrpe plugin with some older version. Changing it solved the problem. I was just wondering and was astonished then..when it was working fine from the commandline and nagios was shooting errors ;) Regards, Gaurav <pre class="moz-signature" cols="72">Disclaimer: This Email message along with any attachments is intended only for the addressee and may contain confidential and/or privileged information. If you have received this message in error, please notify sender immediately and delete this message from your system. If the reader is not the intended recipient then any dissemination, distribution or copy of this communication is strictly prohibited. Reasonable precautions have been taken to ensure that this message is virus-free. However, Subisu Cablenet Pvt. Ltd. does not accept responsibility for any loss or damage arising from the use of this message or attachments.</pre> Hari Sekhon wrote: <blockquote cite="mid:47BAA773.2050000@googlemail.com" type="cite">Gaurav Ghimire wrote: <blockquote type="cite">Hi Tom, Sorry, I missed to point the OS....its Fedora Core 4 both the Monitoring Host and the clients running the daemons are on the same OS. Yes I did check with the FAQs on the site and also visited other related forums, but unfortunately I did not find any such occurrences that matches to what I am facing for now. Most of the related posts that talks of the same problem says they receive the error when running the check_nrpe plugin from console as well. But in my case its not as such. I don't get the error when running it from console, neither any such instance is logged, its just when nagios itselfs runs the plugin I see the error in the web interface. </blockquote> If you run it ok on the command line but Nagios complains then there must be a discrepancy between your nagios config, ie what nagios is running and what you are doing on the command line, perhaps you're not testing as the nagios user account on the command line or there is a parameter problem or something when nagios runs it? I get this error when using -H localhost but not when -H hostname so perhaps it's one of these kinds of issues, try logging the command being executed by echoing it to a file and then run that exact command on the command line. -h </blockquote> </body> </html>