Re: executable won't execute
On Thursday 13 May 2010 20:36:41 Kent West wrote:
> I'm trying to start a daemon for Maple v 14, but when I try to run it,
> the system complains that the file doesn't exist. What's up?
>
> westk[@]goshen.acu.edu]:/usr/local/Maple_Network_Tools/FLEXlm/11.7:> ls -lh
> total 2.8M
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmcksum -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmdiag -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmdown -> lmutil
> -rwxr-xr-x 1 root staff 854K 2010-05-13 16:04 lmgrd
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmhostid -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lminstall -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmremove -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmreread -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmstat -> lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmswitchr -> lmutil
> -rwxr-xr-x 1 root staff 979K 2010-05-13 16:04 lmutil
> lrwxrwxrwx 1 root staff 6 2010-05-13 16:04 lmver -> lmutil
> -rwxr-xr-x 1 root staff 962K 2010-05-13 16:04 maplelmg
>
> westk[@]goshen.acu.edu]:/usr/local/Maple_Network_Tools/FLEXlm/11.7:>
> sudo ./lmgrd
> sudo: unable to execute ./lmgrd: No such file or directory
>
> westk[@]goshen.acu.edu]:/usr/local/Maple_Network_Tools/FLEXlm/11.7:> ldd
> lmgrd
> /usr/bin/ldd: line 117: ./lmgrd: No such file or directory
That ldd can't see it is just weird.
Is the directory NFS-mounted? I have sometimes seen NFS mounts get
confused and do stuff like this, with files showing up in some
queries but not others. Changing the NFS export or mount options
to more careful settings can help (e.g. use "sync", turn off caching, etc.)
Alternatively, I recall that if a file-system is mounted "noexec", it
can give confusing messages when you try to run things from it -- I think
it's usually "permission denied", but maybe my recollection is faulty?
Other than that, given the evidence in the rest of the thread, I'm
going to guess that it's some kind of file-system error. Check the
logs (especially /var/log/kern.log) for errors, maybe fsck the
filesystem, and try again...
-- A.
--
Andrew Reid / reidac@bellatlantic.net
Reply to: