Re: cannot execute binary file

On 05Mar2007 22:36, Pete Masse <petechemistry.montana.edu> wrote:
| I've run into some trouble lately when installing software
on RHES ES 4
| EM64 .  Newly installed executables will not execute. 
Even when including
| the entire path, I still get the error message
"Cannot execute binary
| file".  Permissions are 755, file is owned by root
and belongs to the root
| group.  I tried starting it from a non privileged user and
still the same.
|  SELinux has been disabled in an effort to try and debug
this.  The
| executables I am talking about are supposed to be compiled
for 64 bit
| Linux.
| 
| This has happened to two different executable files so
far, and it seems
| to me that I remember there being some security attribute
that will not
| allow executable files to run just anywhere or something
like that.

What does the "file" command say about these
files,
and what does it say about a working binary file?

What does "ldd" report about these files, too?
Maybe you're missing a
library.
-- 
Cameron Simpson <cszip.com.au> DoD#743
http://www.cskk.e
zoshosting.com/cs/

What's the best platform that Windows NT runs on?
A Kodak carosel slide projector.        - Dvorak

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users

On 06/03/07, Cameron Simpson <cszip.com.au> wrote:
> On 05Mar2007 22:36, Pete Masse <petechemistry.montana.edu> wrote:
> | I've run into some trouble lately when installing
software on RHES ES 4
> | EM64 .  Newly installed executables will not execute.
 Even when including
> | the entire path, I still get the error message
"Cannot execute binary
> | file".  Permissions are 755, file is owned by
root and belongs to the root
> | group.  I tried starting it from a non privileged
user and still the same.
> |  SELinux has been disabled in an effort to try and
debug this.  The
> | executables I am talking about are supposed to be
compiled for 64 bit
> | Linux.
> |
> | This has happened to two different executable files
so far, and it seems
> | to me that I remember there being some security
attribute that will not
> | allow executable files to run just anywhere or
something like that.
>
> What does the "file" command say about these
files,
> and what does it say about a working binary file?
>
> What does "ldd" report about these files,
too? Maybe you're missing a
> library.
> --
> Cameron Simpson <cszip.com.au> DoD#743
> http://www.cskk.e
zoshosting.com/cs/

Also check the permissions on the directory, and verify that
the
filesystem isn't mounted 'noexec'.

Kind regards,

Herta

_______________________________________________
rhn-users mailing list
rhn-usersredhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users