Hullo there,
I've been setting up a debian box to be a clone of several other like boxen. The new box has amd64 architecture and the old i386. Apart from that they are all still on debian sarge, 2.6 kernels.
One thing all the boxen have in common is that they share files over an nfs mount from a server. Some of the files are binary executables.
Now, on the new box, they simply won't run: I get the error
balloon@capirossi:~$ /home/balloon/bin/balloon-audio-off bash: /home/balloon/bin/balloon-audio-off: No such file or directory
The same error appears when running it as root.
The file is executable. The selfsame file also runs no problem from the other computers using it. All I know about the file is that it invokes the bash shell and that it is sending data to the parallel port.
I put together a test bash script to idiot check bash and that ran ok.
I'm baffuffled.
Thanks, Jenny
On Tue, Nov 28, 2006 at 11:44:26AM +0000, Jenny Hopkins wrote:
Hullo there,
I've been setting up a debian box to be a clone of several other like boxen. The new box has amd64 architecture and the old i386. Apart from that they are all still on debian sarge, 2.6 kernels.
One thing all the boxen have in common is that they share files over an nfs mount from a server. Some of the files are binary executables.
Now, on the new box, they simply won't run: I get the error
balloon@capirossi:~$ /home/balloon/bin/balloon-audio-off bash: /home/balloon/bin/balloon-audio-off: No such file or directory
The same error appears when running it as root.
The file is executable. The selfsame file also runs no problem from the other computers using it. All I know about the file is that it invokes the bash shell and that it is sending data to the parallel port.
I put together a test bash script to idiot check bash and that ran ok.
It sounds as if the #! at the beginning of the script is pointing at the wrong location for bash (or at least a wrong location for something).
Look at the first line of /home/balloon/bin/balloon-audio-off and see if what it points at exists (and is executable) on the system where it fails to run.
On 28/11/06, cl@isbd.net cl@isbd.net wrote:
It sounds as if the #! at the beginning of the script is pointing at the wrong location for bash (or at least a wrong location for something).
Look at the first line of /home/balloon/bin/balloon-audio-off and see if what it points at exists (and is executable) on the system where it fails to run.
Thanks, Chris. I can't see inside the file, but I did do a 'which bash' on the new box and on the one on which the script runs, and both return the same: balloon@capirossi:~/bin$ which bash /bin/bash
ls -l /bin/bash -rwxr-xr-x 1 root root 729640 2005-05-02 23:39 /bin/bash
Is this an adequate test?
Thanks,
Jenny
On 28-Nov-06 Jenny Hopkins wrote:
On 28/11/06, cl@isbd.net cl@isbd.net wrote:
It sounds as if the #! at the beginning of the script is pointing at the wrong location for bash (or at least a wrong location for something).
Look at the first line of /home/balloon/bin/balloon-audio-off and see if what it points at exists (and is executable) on the system where it fails to run.
Thanks, Chris. I can't see inside the file,
Hmmm -- how come you can't see inside the file? Whatever the reason, it would be worth going to some trouble to make it possible to read the file yourself, otherwise you could spend a lot of time shooting in the dark.
Good luck again! Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 28-Nov-06 Time: 12:10:10 ------------------------------ XFMail ------------------------------
On 28-Nov-06 cl@isbd.net wrote:
On Tue, Nov 28, 2006 at 11:44:26AM +0000, Jenny Hopkins wrote:
Hullo there,
I've been setting up a debian box to be a clone of several other like boxen. The new box has amd64 architecture and the old i386. Apart from that they are all still on debian sarge, 2.6 kernels.
One thing all the boxen have in common is that they share files over an nfs mount from a server. Some of the files are binary executables.
Now, on the new box, they simply won't run: I get the error
balloon@capirossi:~$ /home/balloon/bin/balloon-audio-off bash: /home/balloon/bin/balloon-audio-off: No such file or directory
The same error appears when running it as root.
The file is executable. The selfsame file also runs no problem from the other computers using it. All I know about the file is that it invokes the bash shell and that it is sending data to the parallel port.
I put together a test bash script to idiot check bash and that ran ok.
It sounds as if the #! at the beginning of the script is pointing at the wrong location for bash (or at least a wrong location for something).
Look at the first line of /home/balloon/bin/balloon-audio-off and see if what it points at exists (and is executable) on the system where it fails to run.
That's a possible source of the problem. However, messages like
bash: /some/program: No such file or directory
can arise whenever something within /some/program fails to find a file or directory it is looking for, and what that "something" is may not be obvious.
The only sure way to track down this kind of thing is to work explicitly through the script, and observe which part of it is going wrong!
Good luck, Jenny! Ted.
-------------------------------------------------------------------- E-Mail: (Ted Harding) Ted.Harding@nessie.mcc.ac.uk Fax-to-email: +44 (0)870 094 0861 Date: 28-Nov-06 Time: 12:00:00 ------------------------------ XFMail ------------------------------
On Tue, Nov 28, 2006 at 11:44:26AM +0000, Jenny Hopkins wrote:
I've been setting up a debian box to be a clone of several other like boxen. The new box has amd64 architecture and the old i386. Apart from that they are all still on debian sarge, 2.6 kernels.
One thing all the boxen have in common is that they share files over an nfs mount from a server. Some of the files are binary executables.
Now, on the new box, they simply won't run: I get the error
balloon@capirossi:~$ /home/balloon/bin/balloon-audio-off bash: /home/balloon/bin/balloon-audio-off: No such file or directory
The same error appears when running it as root.
The file is executable. The selfsame file also runs no problem from the other computers using it. All I know about the file is that it invokes the bash shell and that it is sending data to the parallel port.
What do "file /home/balloon/bin/balloon-audio-off" and "ldd /home/balloon/bin/balloon-audio-off" and "uname -a" say? I suspect your issue is that you're trying to run an i386 binary on an amd64 machine in 64bit mode and that won't work unless you're running it in a chroot AIUI.
J.
On 28/11/06, Jonathan McDowell noodles@earth.li wrote:
What do "file /home/balloon/bin/balloon-audio-off" and "ldd /home/balloon/bin/balloon-audio-off" and "uname -a" say? I suspect your issue is that you're trying to run an i386 binary on an amd64 machine in 64bit mode and that won't work unless you're running it in a chroot AIUI.
Jonathan: Thanks, I think you may suspect correct:
balloon@capirossi:~/bin$ file balloon-audio-off balloon-audio-off: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.30, dynamically linked (uses shared libs), not stripped balloon@capirossi:~/bin$ ldd balloon-audio-off /usr/bin/ldd: line 1: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) balloon@capirossi:~/bin$ uname -a Linux capirossi 2.6.16-2-amd64-k8 #2 Fri Jun 2 17:23:35 UTC 2006 x86_64 GNU/Linux balloon@capirossi:~/bin$
Many many thanks. I'll have a look about for docs on this chroot AIUI you speak of. And contact the author in case there is something he can do with the compilation.
Grateful, Jenny
On Tue, Nov 28, 2006 at 12:05:07PM +0000, Jenny Hopkins wrote:
On 28/11/06, Jonathan McDowell noodles@earth.li wrote:
What do "file /home/balloon/bin/balloon-audio-off" and "ldd /home/balloon/bin/balloon-audio-off" and "uname -a" say? I suspect your issue is that you're trying to run an i386 binary on an amd64 machine in 64bit mode and that won't work unless you're running it in a chroot AIUI.
Jonathan: Thanks, I think you may suspect correct:
balloon@capirossi:~/bin$ file balloon-audio-off balloon-audio-off: setuid setgid ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.30, dynamically linked (uses shared libs), not stripped balloon@capirossi:~/bin$ ldd balloon-audio-off /usr/bin/ldd: line 1: /lib/ld-linux.so.2: No such file or directory ldd: /lib/ld-linux.so.2 exited with unknown exit code (127) balloon@capirossi:~/bin$ uname -a Linux capirossi 2.6.16-2-amd64-k8 #2 Fri Jun 2 17:23:35 UTC 2006 x86_64 GNU/Linux balloon@capirossi:~/bin$
Many many thanks. I'll have a look about for docs on this chroot AIUI you speak of. And contact the author in case there is something he can do with the compilation.
Orrrrrrr...
apt-get install ia32-libs
Should weork for that case, assuming that doesn't use any other libraries.
HTH, HAND.
On 28/11/06, Brett Parker iDunno@sommitrealweird.co.uk wrote:
apt-get install ia32-libs
Aaaaaaaah! Success.
balloon@capirossi:~/bin$ ./balloon-audio-off using printer port at 378 usage: ./balloon-audio-off [-p <port address>] <1/0> Set Balloon board's AUDIO_OFF lines to 1 or 0
Many thanks, Brett, and all. No way would I have sussed that. Bloody amd64, mutter, mutter.
Thankyou! Thankyou!
Jenny
On 28/11/06, Jenny Hopkins hopkins.jenny@gmail.com wrote:
I'll have a look about for docs on this chroot AIUI you speak of. And contact the author in case there is something he can do with the compilation.
Ha ha ha! I just found out that AIUI is an acronym for As I Understand It rather than some weird chroot Artificial Intelligence UI. Still, you'd all be disappointed if I did a post without something idiotic in it :-)
Jen
-
Brett Parker -
cl＠isbd.net -
Jenny Hopkins -
Jonathan McDowell -
Ted.Harding＠nessie.mcc.ac.uk