When I login using SSH, all I can see is this...

-bash: /usr/bin/id: cannot execute binary file
-bash: [: : integer expression expected

I couldn't do anything in here. Commands such as halt, poweroff, reboot will return command not found.

How can I fix this? I am using Debian Squeeze Linux

  • 6
    What did you do to that machine? – slhck Jun 12 '12 at 21:32
  • 1
    the very last thing I did was install logwatch. Nothing else. – superuser Jun 12 '12 at 21:33
  • 3
    PATH is an environment variable which contains a list of folders which the shell searches for programs. ls for example, usually refers to /bin/ls, and your shell finds it by going through the folders listed in PATH one-by-one until it finds it, or if it doesn't find it in any of them, it gives up. I suppose a better starting point would be, what is the output of echo $PATH ? (edit: the export command is a way to define an environment variable in bash.) – Darth Android Jun 12 '12 at 21:41
  • 1
    Ah... I warned you not to shut the system down :P Can you get console access to it (physical monitor+keyboard attached)? Try booting the system in single-user mode (might be labelled as recovery mode) and see if you can get to a root shell. – Darth Android Jun 12 '12 at 21:51
  • 2
    @David you won't see any output after typing export PATH=/bin:/user/bin:/sbin:/usr/sbin. It's a silent command. – Ben Richards Jun 12 '12 at 21:57
up vote 73 down vote accepted

Usually that error message means Linux doesn't recognize the file as a shell script or as an executable file.

Typically the cause is running an executable on the wrong architecture - if you try to run x86 executables on an ARM CPU, this message comes up.

Did /usr/bin/id get overwritten, possibly?

  • 12
    "if you try to run x86 executables on an ARM CPU, this message comes up." That was EXACTLY what caused it. Thanks everyone for your inputs! – superuser Jun 13 '12 at 4:18

Try to run it using ./executablefilename instead of using sh executablefilename. It's not a shell script after all.

  • I had this problem when trying to run kiwix-serve on my raspberry pi. My overall solution I believe was to adjust the file permissions (it was not set to executable by anyone by default) and then ran it as ./kiwix-serve – cchapman Jun 19 at 15:38

The problem is running a binary for a different processor architecture. You can use objdump (from binutils) to check architecture of binaries. You can use uname to check architecture of a machine.

e.g. I encountered this error "cannot execute binary file" when installing FF.Communicator - a firefox plugin for chrome (so I can run pages that use java applets).

  • objdump shows the binary is 64-bit elf64-x86-64
  • uname shows my machine is 32-bit i686

    $ ./FF.Communicator bash: ./FF.Communicator: cannot execute binary file $ uname -mpio i686 i686 i386 GNU/Linux $ objdump -a ./FF.Communicator ./FF.Communicator: file format elf64-x86-64 ./FF.Communicator

  • objdump on a working binary on my machine shows it is 32-bit elf32-i386

    $ objdump -a /bin/ls /bin/ls: file format elf32-i386

Using these tools you can check architectures of machines and binaries - not just intel architectures but any processor.

I'm making some wild guesses here, but it looks like the following is happening:

  1. You log in over SSH, triggering bash to run your ~/.profile or ~/.bashrc to set up your environment for you (this is normal).
  2. At some point it tries to execute /bin/id to get your uid, which fails, causing integer expression error, and terminating the script before it can set up your $PATH.
  3. Because your $PATH is not set, bash is only able to run commands with the full path specified.

Use export PATH=/bin:/usr/bin:/sbin:/usr/sbin to fix the $PATH issue until you can fix the root cause of /bin/id failing.

binary file consists of machine instructions the processor can understand. Your operating system does not mean the same executable will run. move back and forth between the processor instruction set compatible with will usually work well, if they are not compatible CPU will not be able to understand instructions.

You are running wrong version of the installer, for example, 64bit machine and trying to install 32bit version of the installer.

Your Answer

 

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.