Hello,

I am curious what could cause bash to describe a file as not existant however it is obviously existant with proper permissions with a quick 'ls' command. This has occured on a Ubuntu Server Installation and it has also been attempted with ' Sudo '. I am curious what would be the default troubleshooting steps in such as situation, what causes this?

I am aware the path to the file is correct, full path and direct current directory has been specified with same results.

Thanks!

have you tried to edit the file or are you executing it? have you tried name completion to finish typing it (maybe a trailing whitespace char for instance.) Have you tried to open it with say a file manager?

Please post the commands and output you use

Unfortunately I am not able to actually display these commands or output due to certain circumstances unless I personally modify all the details out which would be believed to make the information useless in the first place. It is simply being executed itself with '$./FILENAME', '$SUDO ./FILENAME ' or '$/path/to/directory' and I am simply being given the generic bash, ' No such file or directory ' although it does display and is existant.

Due to these circumstances is why I more or less requested general possibilities.

I do enjoy the idea of the possibility of special-character or white-space.

Could this have anything to do between Arch, such as running a 64-bit execute without 64-bit libraries? Is there a way to tell which ARCH the file type is?

Is the file executable ?

I am able to execute file on the 'file' and get, ' ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not stripped '.

I think repo was asking-- is the execute bit set--

chmod o+x filename

Then try to run it again

Yes, proper permissions do exist, with full executable bits.

If this was not so I believe this would also specify a permission denied error as I did a quick test.

Attempting as ' su - ' provides the same results.

Creation of a test file in the same path and permissions works fine.

I am starting to believe there's an issue with the file itself, although the error message is what is throwing me off.

You are aware Linux is case sensitive, right?

Have you tried copying the file from the ls output and pasting it into the command. (Copy by selecting it, paste by middle-clicking). That would deal with anything like odd characters.

Just a couple of quick thoughts.

Is it possible that either:
a) The file/program you are attempting to execute has leading or trailing white characters (ie. spaces, tabs, etc..) in it's name ?
b) The file/program is missing some libraries ? (ie. bash is complaining about the missing libraries and not the missing file)
Does "ldd ./FILENAME" report any missing libraries ?

--ET

gives the architecture. This needs to match the one given by the

command!

Has anyone here ever known a "branded" (non-generic) bash?

One clear specific information about the problem is worth better than a thousand blahs of gorgeous flowery talk.

OMG! Please speak English.

Unless you tell us what you have done, what files, which directories and reported error...... well, there is no end for grandiose oration.



we wait.

Hi folks

Did anyone notice that the last reply to this thread before today, was back in January?? And the OP has not logged in since March.

Cheers!

Oooopss!

Ha ha ha I didn't imagine I was helping out a ghost. I didn't bother checking the dates. I was merely using the Zero Reply button hoping to become useful to the community when my time affords this pleasure.

And (I'm curious) how did the "Zero reply button" get you here, to a thread with 10+ replies?