Assaf, Could you explain with a little more detail how I could recover the "check_tcp" from the source exactly? thanks <div class="gmail_quote">On Tue, Jul 12, 2011 at 10:21 AM, Assaf Flatto <<a href="mailto:nagios@flatto.net">nagios@flatto.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">dOE wrote: > Hi, > > I inadvertently deleted/overwrote the "check_tcp" file in ../libexec. > I tried copying the file back from another Nagios instance (same build > 3.0.3), but when I execute it it I get a "No such file or directory". > My permissions for the file are no different than other "checks_" in > the directory. Is there something else I need to do other than copy a > file from another Nagios instance? > > > rwxrwxr-x 1 nagios root 76K 2011-07-01 13:47 check_tcp > > > Thanks > ------------------------------------------------------------------------ from what your title say you are getting the error when trying to execute the file locally and fail . Are you sure the file was copied successfully ? If you installed the plugins from source you can go the the source code directory and do "make install" and it place the plugins in the directory again . ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. <a href="http://p.sf.net/sfu/splunk-d2d-c2" target="_blank">http://p.sf.net/sfu/splunk-d2d-c2</a> _______________________________________________ Nagios-users mailing list <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </blockquote></div>