./check_tcp: No such file or directory

[dOE]

Ok, I think I may have figured out the issue.

It seems the check_tcp I copied was 32-bit, and all of the other "checks"
are 64-bit (the server itself is 64-bit OS as well.

*check_tcp: ELF 32-bit *LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

*check_ntp: ELF 64-bit* LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

Seeing that I do not have any other 64-bit Nagios instances running I may
need to run another install on a 64-bit OS just to harvest the "check_tcp"
from it.

On Tue, Jul 12, 2011 at 10:03 AM, dOE <doepain at gmail.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20110712/9b8c7451/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
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.
http://p.sf.net/sfu/splunk-d2d-c2
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null