Wednesday, February 9, 2011

Resolution for bash orted command not found

If you faced an issue like this below, it is likely due to your path-ing issue in an non-interactive mode. See Blog Entry Unable to source path during non-interactive ssh session

bash: orted: command not found
--------------------------------------------------------------------------
A daemon (pid 12639) died unexpectedly with status 127 while attempting
to launch so we are aborting.


There may be more information reported by the environment (see above).


This may be because the daemon was unable to find all the needed shared
libraries on the remote node. You may set your LD_LIBRARY_PATH to have the
location of the shared libraries on the remote nodes and this will
automatically be forwarded to the remote nodes.
--------------------------------------------------------------------------

You can verify by using this niffy commands to check
$  ssh remote-server-name which orted
You should get something like the return value below if you have source correctly in your .bashrc and .bash_profile
$ /usr/local/mpi/intel/bin/orted
If not, you will get
which: no orted in (/usr/local/bin:/bin:/usr/bin)
Either you put your binaries in the standard path like /usr/local/bin /bin /usr/bin or you have to source correctly in your .bashrc and .bash_profile

2 comments:

litteboy said...

Thank you very much!. I got this error because I set PATH and LIBRARY PATH in /etc/profile instead in .bashrc

karthik bharadwaj said...

Thanks , This was really helpful